none
BIzTalk migration from 2006 to 2010 RRS feed

  • Question

  • We are running BizTalk server 2006 now and are trying to migrate all existing applications to 2010. Can we export existing applications to MSI and import them into 2010? Or do we have to convert each project using Visual Studio 2010 and deploy?
    Thursday, July 18, 2013 6:11 PM

Answers

  • Well, it's very early to tell, but because the major shift from 2010 to 2013 was on the Dev side (VS2010 to VS2012) forward compatibility on the runtime side should be very good.

    However, keeping the Design and Runtime in sync is preferred.

    • Marked as answer by Pengzhen Song Thursday, July 25, 2013 12:01 PM
    Thursday, July 18, 2013 8:10 PM
    Moderator

All replies

  • No. See this thread that answers all your questions http://social.msdn.microsoft.com/Forums/en-US/1525e180-1d2e-43cc-b1b3-a5df80cc951e/migration-from-2006-to-2010
    Thursday, July 18, 2013 6:24 PM
  • Keep in mind, you're skipping 2 versions.  Few points:

    1. The applications may run unchanged when exported from 2006.
    2. If you are using TPM/EDI, you will have to update code to accommodate Agreements introduced in 2010.
    3. BizTalk Server 2010 shifted to .Net 4.0 while BizTalk Server 2006 is still CLR 2.0 based.
    4. To modify the apps in any way, you will have to upgrade the projects to Visual Studio 2010.
    5. Once one Project is updated, you may have to migrate all of them.

    So, you'll find the consistent recommendation will be to upgrade the Projects to 2010.  By doing so, there won't be any mystery as to their supportability.

    Also, there is no direct Project path from 2006 to 2010.  You will have to migrate to the 2006 R2 or 2009 project system first, then 2010.
    Thursday, July 18, 2013 6:27 PM
    Moderator
  • How about migration from 2010 to 2013? I guess I can use msi without converting projects?
    Thursday, July 18, 2013 7:41 PM
  • Well, it's very early to tell, but because the major shift from 2010 to 2013 was on the Dev side (VS2010 to VS2012) forward compatibility on the runtime side should be very good.

    However, keeping the Design and Runtime in sync is preferred.

    • Marked as answer by Pengzhen Song Thursday, July 25, 2013 12:01 PM
    Thursday, July 18, 2013 8:10 PM
    Moderator
  • Yes that is supported. We successfully completed an "in place" production upgrade from BizTalk 2010 to to BizTalk 2013 without any major issues.
    Friday, July 19, 2013 3:34 AM