Geeks With Blogs
BizTalk with me Arvind Chaudhary

BizTalk projects require some manual intervention in order to upgrade them. First of all make sure that you do not port single BizTalk Project from a solution. So the porting should be done for a complete BizTalk 2006 solution.

Execute the following steps to port a BizTalk solution / project:

  1. Open the projects' solution file (.sln) using a text editor – NotePad++ is recommended.
  2. Remove all the contents (in red below) between (not including) the following elements:
GlobalSection(ProjectConfigurationPlatforms) = postSolution
          {5C48CB6B-AE6F-4288-A8EE-46E352BB730C}.Debug|.NET.ActiveCfg = Debug|Any CPU
          {5C48CB6B-AE6F-4288-A8EE-46E352BB730C}.Debug|.NET.Build.0 = Debug|Any CPU
          {5C48CB6B-AE6F-4288-A8EE-46E352BB730C}.Debug|Any CPU.ActiveCfg = Debug|Any CPU
          {5C48CB6B-AE6F-4288-A8EE-46E352BB730C}.Debug|Any CPU.Build.0 = Debug|Any CPU
         
EndGlobalSection
         
You should see the following once you have removed the contents:
     GlobalSection(ProjectConfigurationPlatforms) = postSolution                EndGlobalSection
     
     Note: There should not be any line left between GlobalSection and EndGlobalSection.

3. Open the pack’s solution file (.sln) using Visual Studio 2008. This will invoke the upgrade wizard. NOTE: If you are connected to Team foundation server, the files should be checked out from TFS during this procedure.

4. Click Next to proceed with the upgrade. As per the sample below, note that the files should be checked out from TFS. No backup will be performed by default which is acceptable as TFS will hold the original source code

 

5. Click Finish to execute the Visual Studio Upgrade wizard. If you have performed the steps above correctly you should see “All projects converted successfully.” If not, ensure that you check “Show the conversion log when the wizard is closed”. This will allow you to review the conversion status of each project for errors

 

6. Exit Visual Studio 2008.

7. Again, open the projects' solution file (.sln) using a text editor – NotePad++ is recommended.

8. Remove all the contents (in red below) between (not including) the following elements:

GlobalSection(ProjectConfigurationPlatforms) = postSolution
          {5C48CB6B-AE6F-4288-A8EE-46E352BB730C}.Debug|.NET.ActiveCfg = Debug|Any CPU
          {5C48CB6B-AE6F-4288-A8EE-46E352BB730C}.Debug|.NET.Build.0 = Debug|Any CPU
          {5C48CB6B-AE6F-4288-A8EE-46E352BB730C}.Debug|Any CPU.ActiveCfg = Debug|Any CPU
          {5C48CB6B-AE6F-4288-A8EE-46E352BB730C}.Debug|Any CPU.Build.0 = Debug|Any CPU
         
EndGlobalSection
         
You should see the following once you have removed the contents:
     GlobalSection(ProjectConfigurationPlatforms) = postSolution EndGlobalSection

9. Once all .btproj files have been updated, open the solution using the Visual Studio 2008 IDE. Navigate to the Configuration Manager. 

 

10. For each configuration type (Debug / Release) make sure you select “Build” for all projects and “Deploy” for BizTalk projects. See below for an example.

 

11 For all the BizTalk Projects in the solution , open the assembly info file(assemblyInfo.cs) and add following attribute if not already present:

 [assembly: Microsoft.XLANGs.BaseTypes.BizTalkAssembly(typeof(Microsoft.BizTalk.XLANGs.BTXEngine.BTXService))]

12. Compile your solution and make sure it builds fine

 

 

 

 

.

 

Posted on Tuesday, March 23, 2010 2:42 PM | Back to top


Comments on this post: Useful Tips for BizTalk 2006 to BizTalk 2009 Porting

# re: Useful Tips for BizTalk 2006 to BizTalk 2009 Porting
Requesting Gravatar...
Hey Nice Tips.
Left by Aanchal Harit on Mar 27, 2010 7:54 PM

Your comment:
 (will show your gravatar)


Copyright © Arvind Chaudhary | Powered by: GeeksWithBlogs.net