The situation is complicated by two things: the change in project definitions between VS 2003 and VS 2005, and of course the migration from .NET 1.1 to .NET 2.0 (there should be no complication by .NET 3.0 with BizTalk 2006 R2 as .NET 2.0 exists as-is in 3.0).
Depending on the solution, some of the following items may not apply, and there may be other items not mentioned you will need to take care of (ie referencing deprecated classes, method overloads etc).
- Migrate the solution to VS 2005 by simply opening the VS 2003 .sln file. Complete the steps of the solution migration wizard. This will generate a report of the items you may need to fix (esp deprecated classes)
- Once in the solution, at the BizTalk Project level you will need to do the following:
- If you have web references in your project, you will need to rebuild them.
- Delete each web reference and re-add them with the same name
- If you use Dynamic web references, ensure that property is selected
- Add a reference to System.Configuration if it is not there already (the compiler will fail otherwise)
- Open the project's properties
- Assign a default BizTalk Configuration Database
- Assign an Application Name
- For each schema in your solution that uses promoted properties
- Open the 'Show Promotions' dialog. This will rebuild the xsd's code-behind (.cs)
- For each orchestration with a web-port
- Delete the configured web port (since you regenerated the web reference)
- Re-add the web port with the same name, ensuring it is a Dynamic web port if necessary
- Re-assign message types for messages defined in Orchestration Explorer
- Re-connect send/receive shapes if necessary
Performance Warning: marking service 'OrchestrationName' as a longrunning transaction is not necessary and incurs the performance penalty of an extra commit
For orchestrations where long-running was not necessary (ie do not contain send/receive pattern or other long-running transactions), I have since changed them to use Transaction Type of None. Hopefully we will see a reduction of database chatter for these orchestrations when we benchmark the changes.
Clearly the migration is not trivial, though hopefully yours is smooth and relatively quick.