Geek Answers Handbook

Tridion migration issues from SDL Tridion 5.3sp1 to 2011sp1

We need to migrate Tridion 5.3sp1 to 2011sp1,

If someone has some experience with this type of migration,

we use only the following functions.

  • DWT (I do not see big changes in it)
  • Tom.net
  • TOM (TDSEClass)

What needs to be changed? What are the areas of pain?

Where can I get more information on the Internet?

+4
source share
2 answers

Based on my experience:

  • TOM code will work. You should rewrite it instead of using CoreService, but this should not be a priority, you can do it after the update. You really have to do this because it creates a dependency on COM +, which Tridion gradually stops. As far as I know, COM + will be optional in the next version of Tridion and may not be available at all in the release.
  • TOM.NET on templates may just work, but I think some changes have been made to the Filter classes from 5.3 to 2009. You may need to make a few small changes before they are compiled again, nothing serious.
  • DWT: nothing has changed

The biggest problems I discovered are related to the event system. If you have an old COM + event system, it is still supported, but the cost of not updating to the new TOM.NET-based event system is very fast. COM + errors / memory problems occur even faster with Tridion 2011 than before, it seems that the .NET Marshalling COM server is less and less forgiving over time.

According to Vikas, the best way is to get update scans from people who have done this before, they know what areas of the problem are, and quite often they find extensions that you don’t even suspect were put into action, like Deployer and "incomprehensible" event systems or custom pages (or, starting with the good old days of R5, GUI hacks).

+6
source

Areas of pain depend on your implementation, so you first need to scan for updates from professional or professional specialists or expert partners.

Here is a good list you can read.

Basic code services

+7
source

More articles:


All Articles