I then came to learn that Sitecore 7 was just around the corner, and a tech-pub arragement by Sitecore on May 31st 2013 convinced me to take on this version instead of the 6.6 update 5. The main reason for the choice to upgrade to Sitecore 7 directly was that I was assured by members of the Sitecore-team behind the Sitecore 7 development, that the upgrade was merely a developer-centric feature-upgrade (not a very common thing in the Sitecore world), meaning that the new Linq provider, the item-buckets and the pluggable search was the only actual add-on of the upgrade (plus a few bugfixes).
Of course we wanted to get hold of these features as well and therefore pursued the version 7.0 installation.
Two interesting things to note though:
- Sitecore 7 is built targetting .net 4.5
- The IIS application pool must be changed to run 4.5 in order to run the new site
Sitecore 7 on .net 4.5
This change means that you need to upgrade your Visual Studio Solution to VS 2012 (if your solution is based on Visual studio 2010 or lower), because you are not able to target 4.5 in VS 2010.
Not that the installation of VS 2012 it-self was a problem for me personally - I have already made the transition to VS 2012 long ago - but the virtual machine the development-solution was using was not compatible with VS 2012 !
IIS application-pool on 4.5
This might turn out to be a problem for you if third-party DLLS are not able to run under this configuration.
Recommendation
Upgrade your solution to VS 2012 prior to installing the Sitecore 7 upgrade and making the necessary changes to your solution. This will enable you to address the problems one at a time and not pile up all the challenges you are facing.
Conclusion
Be sure that you are able to upgrade your solution to VS 2012 prior to the Sitecore 7 installation.
Hope that the description above will help you do a better estimate on your upgrade and help you be better prepared for the task.
No comments:
Post a Comment