Best Practices for Upgrading to Sitecore 8.2
Hi All,
For those who plan to upgrade your Sitecore version to 8.2 here is a wonderful video and good blog post about best practices on how to do that .
Sitecore, problem solutions and discussions
Hi All,
For those who plan to upgrade your Sitecore version to 8.2 here is a wonderful video and good blog post about best practices on how to do that .
First of all I would like to describe the main problem here which is creating Web API and MVC routes which will handle the corresponding requests correctly.
From technology point Web API is designed on much more on Lower level then MVC, to be clear it is not better or worse but they are used for different things, however MVC is build on top of the Web Api.
But as the MVC comes on top of the Web API routes that are different first go through the MVC Routes and if they cannot be found then go deeper in the Web Api routes.
Imagine if you have two routes with same names /GetMyList in MVC and /GetMyList in Web API, there is a big chance that the route handler will be confused.
In Sitecore regular instance you can just define the route with RouteTable.Routes.MapRoute() or RouteTable.Routes.MapHttpRoute() and because there is no other api routes they will work, however in habitat you need to be more careful which function do you use in order create route.
This is because habitat already comes with the a lot of different pipeline processors which are pre-configured and this can be a problem when mapping new routes especially if you don’t know or don’t consider the already mapped routes from habitat.
Best practice in habitat would be to separate the web api routes from MVC routes and also always use the MapHttpRoute for Web API and MapRoute For MVC.
Keep in mind that one other good practice is to always separate Web API and MVC routes in separate folder and also the names of the routes should bed different. Please see the attached picture.
One thing I forgot to mention which is really important is that in habitat for every project have you maps the Web Api or MVC routes in the RegisterWebApiRoutes.CS in the pipeline folder of that project, and normally add the “pipeline”(RegisterWebApiRoutes.cs) to the pipeline processor in app_config/include/feature/nameOftheProject.Config in order to be properly executed and register the proper routes.
I hope that you will find this post useful and it will give you boost up if you stuck with Web Api and MVC Routes in Habitat project.
Hi as I mentioned in the introduction to Habitat post I would like to note some things on installing Habitat basically what do you need to take care and know before starting.
First of all and most easiest one is downloading the habitat solution from GitHub and you can do at least in two ways.
That should be it, everything else should be as it is described on the Getting Started
Please keep in mind the following things and settings :
1. Unblock, Make Sure permissions are set correctly
2. Get all dependencies and requirements
3. Make sure that everything you run is as Administrator
3. Make sure that you have set proper paths to the Gulp Configs
Source location: C:\projects\Habitat\
Website location: C:\websites\Habitat.dev.local\
Website URL: http://habitat.dev.local/
To change the standard location of the source files, website files and website URL, modify the following files:
gulp-config.js
Publishing targets
z.Habitat.DevSettings.config
I hope that this will help you
Refereeing the the GitHab repository for Habitat ( https://github.com/sitecore/habitat/wiki )
Habitat is a Sitecore solution example built on a modular architecture. The architecture and methodology focuses on:
Habitat Makes implementation of new functionality in Sitecore much more easier and is also good practice for enterprise solution and developing your Sitecore solution with the proper Sitecore Helix guidelines.
There is a lot of documentation how to setup the Habitat project on your sitecore instance written on net, however the installation can be a little bit tricky and you could easily waste a lot of time. Once it is setup correctly it works as charm.
I will try to write some tutorial on how to install habitat ( adapt the already existing one, withe detailed explanation for the tricky parts ).
Meanwhile , you can find a lot of information on the provided videos and links below.
For more information about the architecture and the principles and conventions behind it, please see the Sitecore Helix guidelines
Video introductions:
Also very good documentation on the Sitecore Helix guidelines.
And here is example of the how page should look like when you install Habitat over your Sitecore instance.
Sitecore is a customer experience management company that provides web content management and multi-channel marketing automation software.
Based on the .Net framework Sitecore platform is one of the most widely used enterprise content management solution.
I have found one very good article that explains the core values of the Sitecore platform, here are some links and quotes about Sitecore :
Sitecore is an ASP.Net-based WCM web application technology which houses everything your marketing team needs to store, manage, analyze, and update your website content in a single unified solution. After the initial development of your website using ASP.NET MVC the management ownership is placed in the hands of your marketing team instead of IT to create content, forms, and articles and measure the value of the content throughout its life cycle.
There are many notable WCM Features in Sitecore which we’ll dive into deeper on future articles:
A unified platform and strategy is needed by nearly every business to find, funnel, and convert prospects into life-long customers. Sitecore provides the tool set your marketing team needs to efficiently engage customers no matter the channel. We have only looked at a few features of Sitecore so far, but we will cover the many other capabilities like the Digital Marketing System (DMS), email campaign management, CRM integration, and more in future articles.
Full text Here
Additional links :
https://kb.sitecore.net/
Hi As I mentioned in the About Page ( I hope that you have been there already , if not please check it out ).
I wanted to start blog in order to connect or reach out to other Sitecore developers and to write about problems, solutions, raise some discussion regarding the Sitecore web content management.
I hope that you will find a lot of useful staff here on my blog and that we can share knowledge through the Sitecore community.
I am looking forward for comments, critics and new stuff 😀