| description | title | ms.custom | ms.date | ms.service | ms.reviewer | ms.suite | ms.topic |
|---|---|---|---|---|---|---|---|
Learn more about: Migrating a BizTalk Server Project |
Migrating a BizTalk Server Project |
06/08/2017 |
biztalk-server |
article |
[!INCLUDEbtsVStudioNoVersion] projects developed for [!INCLUDEbtsBizTalkServerNoVersion] can be migrated to the newer environments by using [!INCLUDEbtsVStudioNoVersion] conversion. For a list of the supported migration versions, see Supported Upgrade Paths and Installation Guides.
The following table shows how [!INCLUDEbtsbiztalkserver2006r2] project configuration names change, and where some specific configuration properties relocate after the project is converted to a newer [!INCLUDEbtsBizTalkServerNoVersion] project. Most of the [!INCLUDEbtsBizTalkServerNoVersion]-related project settings are located on the Deployment tab of Project Designer.
| [!INCLUDEbtsbiztalkserver2006r2] project | [!INCLUDEbtsBizTalkServerNoVersion] project |
|---|---|
| Embed Tracking Information output configuration property | Define TRACE constant build option on the Build tab of Project Designer |
| Generate Debugging Information output configuration property | Define DEBUG constant build option on the Build tab of Project Designer |
| BPEL Compliance code generation configuration property | BPEL Compliance code generation property in the project properties window |
Note
BizTalk projects now have two build types: Release and Debug, which replaces Development and Deployment of earlier versions. However, you will continue to see the Development and Deployment configurations for the projects that are migrated from [!INCLUDEbtsbiztalkserver2006r2].
[!CAUTION] Only the *.btproj and *.btproj.user project files are backed up as a result of choosing the back up option during the conversion. Other files must be manually backed up.
[!CAUTION] Any customizations to auto-generated items such XSD and ODX files will be lost during conversion. This applies to XSD files generated when a web reference is added to a BizTalk project as well.
[!INCLUDEbtsbiztalkserver2006r2] projects that use Delay Signing may fail during the build process after being converted for [!INCLUDEbtsBizTalkServerNoVersion]. This can happen if Generate serialization assembly build setting for the migrated project configuration is not set to Off.
MSMQT is no longer part of [!INCLUDEbtsBizTalkServerNoVersion]. For more information on how this can affect project migration, see the topic MSMQT Deprecation.
If you attempt to convert a [!INCLUDEbtsbiztalkserver2006r2] project and do not have the solution file you will receive the following error:
Error converting project file. Child element <BIZTALK> of element <VisualStudioProject> is not valid.
Project conversion requires the solution file (.sln) from the [!INCLUDEbtsBizTalkServerNoVersion] project. If the solution file is not available, you must create one with [!INCLUDEbtsVStudioNet2005] and add the [!INCLUDEbtsbiztalkserver2006r2] project to the solution. Then run the [!INCLUDEbtsVStudioNoVersion] conversion wizard.
Note
You may be able to convert the project using only the project file (.btproj) with Visual Studio.