Finally, we launchet one of the biggest upgrade of Umbraco / uCommerce / Windows servers I have ever been involved in.
From Umbraco 4.7.0 to the latest 6.1.5 . From uCommerce 2.0.5 to the latest 4.1.4 . Refactorering solution to fewer projects. From Win7 , IIS7 , MSSQL2008 to latest WinServer 2012 IIS8 , MSSQL 2012. As previously with TeamCity , Subversion and a pipeline of 4 servers (local and demo delveloper , stage , live ) .
http://mit.jp.dk.">Where: Jyllands- Posten commercial team on http://mit.jp.dk . One
of Denmark's largest newspapers , Jyllands- Posten - have here a store
that sells subscriptions and special offers for subscribers.
A team of 5 men worked over a month to get all updates implemented. A large part of the code that uses uCommerce 's API has been rewritten . The
biggest challenges has been setup : config -files and assemblies ,
weird hacks and undocumented new guidelines - especially uCommerce has
been a challenge . Another major challenge has been automated tests that run in a separate project - which also needed updating.
Such large changes have not been able to be part of a normal deployment . We
have set up a parallel line with the upgrade project and continuously
synchronized with normal project which regularly had small updates . A
parallel line of course, provides world of challenges in relation to eg
dns , permits inside and outside gmz since we use a range of services
from third parties.
So - here's how we did it : A : Upgrade uCommerce and solution files - Install uCommerce packets from Umbraco backend. Stepwise. We found this model works: 2.0.5 - > 2.6 -> 2.6.1 -> 3 - > 4 - During the upgrade: the code and settings using uCommerce must also be upgraded. B : Upgrade Umbraco - From an empty folder only with Umbraco 6 : Specify the database and run the installer - Merge Umbraco 's web.config with your own . Do the same for other config files C : Use the upgraded database just replace the files with the updated files ( from A except for the new merged config files)
Oh - by the way : Lots of things can go wrong in such a big upgrade. I will post some more details on our.umbraco.org in the coming days.
From Umbraco 4 to 6 and from uCommerce 2 to 4
Finally, we launchet one of the biggest upgrade of Umbraco / uCommerce / Windows servers I have ever been involved in.
From Umbraco 4.7.0 to the latest 6.1.5 .
From uCommerce 2.0.5 to the latest 4.1.4 .
Refactorering solution to fewer projects.
From Win7 , IIS7 , MSSQL2008 to latest WinServer 2012 IIS8 , MSSQL 2012.
As previously with TeamCity , Subversion and a pipeline of 4 servers (local and demo delveloper , stage , live ) .
http://mit.jp.dk.">Where: Jyllands- Posten commercial team on http://mit.jp.dk . One of Denmark's largest newspapers , Jyllands- Posten - have here a store that sells subscriptions and special offers for subscribers.
A team of 5 men worked over a month to get all updates implemented. A large part of the code that uses uCommerce 's API has been rewritten . The biggest challenges has been setup : config -files and assemblies , weird hacks and undocumented new guidelines - especially uCommerce has been a challenge . Another major challenge has been automated tests that run in a separate project - which also needed updating.
Such large changes have not been able to be part of a normal deployment . We have set up a parallel line with the upgrade project and continuously synchronized with normal project which regularly had small updates .
A parallel line of course, provides world of challenges in relation to eg dns , permits inside and outside gmz since we use a range of services from third parties.
So - here's how we did it :
A : Upgrade uCommerce and solution files
- Install uCommerce packets from Umbraco backend. Stepwise. We found this model works: 2.0.5 - > 2.6 -> 2.6.1 -> 3 - > 4
- During the upgrade: the code and settings using uCommerce must also be upgraded.
B : Upgrade Umbraco
- From an empty folder only with Umbraco 6 : Specify the database and run the installer
- Merge Umbraco 's web.config with your own . Do the same for other config files
C : Use the upgraded database just replace the files with the updated files ( from A except for the new merged config files)
Oh - by the way :
Lots of things can go wrong in such a big upgrade. I will post some more details on our.umbraco.org in the coming days.
--
Ulrik Ricco Hansen, [email protected]
Certified Umbraco developer level 2
is working on a reply...