BizTalk 2010 Project file version numbers and structure differ between new and upgraded projects
1/7/2011 4:31:16 AM
User(s) can reproduce this bug
First a quick point; your Submit Feedback form only allows me to select the BizTalk 2010 Beta for the product version - I am not using the beta, I am using the RTM version. So all feedback here relates to BizTalk 2010 RTM. Thanks.
I've just successfully completed upgrading a BizTalk 2006 project to BizTalk 2010.
I had a few problems resulting from using the Deployment Framework For BizTalk (changes to Build Configuration names) which caused me to create a new BizTalk 2010 solution with schema and orchetration projects to use as a point of reference. During this process I noticied a few discrepancies between the Project File generated by Visual Studio 2010 when creating a new BizTalk 2010 project compared to those created by Visual Studio 2010 when it upgraded the existing BizTalk 2006 projects.
Whilst this doesn't seem to be causing any problems I am a little surprised by this as it wasn't what I expected (I would have expected identical structures, version numbers, etc.) and I want to be sure I understand what it means and whether there will be any implications later on.
Here's a summary of the variations I have noticed:
1) The ProductVersion element has a value of 8.0.30319 on the upgraded project, whereas on the new project it is 9.0.21107.
2) In the first PropertyGroup of the upgraded project file there are a number of extra elements not present in the new project file: AssemblyOriginatorKeyFile (moved to its own PropertyGroup in new project file), DelaySign, FileUpgradeFlags, SignAssembly (moved to its own PropertyGroup in new project file), ModifySolutionConfiguration.
3) In the upgraded project file the XLANg tags in the ItemGroup elements defining the project items (orchestrations in this case) contain additional TypeName and Namespace elements.
Depending on exactly what is contained in your project there may be other variations I've not picked up.
For me these variations simply didn't make sense. If I want a BizTalk Orchestration project for example in VS.NET 2010/BTS 2010, then whether I created it from scratch or upgraded it from a previous BTS 2006 project my project files should be identical (generated guids etc. excepted).
I'd be grateful if someone could explain why these variations exits, whether it's by design, why it's by design and whether this could cause problems down the line.
Thanks in anticipation.
BizTalk 2010 Beta
Take an existing BizTalk 2006 project and upgrade it to BizTalk 2010 using the VS.NET 2010 Ultimate upgarde wizard.
Compare the contents of the project file to a brand new BizTalk 2010 project file created directly in VS.NET 2010.
to post a comment.
Please enter a comment.
to post a workaround.
Please enter a workaround.
© 2014 Microsoft