Search

Automated build of BizTalk 2009 project fails in TFS 2010 beta 2 Build Server by JarinK

Resolved
as Won't Fix Help for as Won't Fix

3
0
Sign in
to vote
Type: Bug
ID: 529553
Opened: 1/30/2010 6:22:53 AM
Access Restriction: Public
0
Workaround(s)
3
User(s) can reproduce this bug
I'm getting compilation errors due to the conflicts in .NET Framework versions 2.0 and 4.0 when building BizTalk 2009 project using TFS 2010 beta 2 Build Server. I could not find a way to force build to use only .net framework 2.0 assemblies.

Here is a snippet from the build log:
CoreCompile:
C:\Windows\Microsoft.NET\Framework\v3.5\Csc.exe /noconfig /nowarn:1701,1702 /errorreport:prompt /warn:4 /define:TRACE /reference:C:\Windows\Microsoft.NET\Framework\v2.0.50727\System.Configuration.dll /reference:C:\Windows\Microsoft.NET\Framework\v2.0.50727\System.dll /reference:C:\Windows\Microsoft.NET\Framework\v2.0.50727\System.Xml.dll /reference:"C:\Program Files\Microsoft BizTalk Server 2009\Microsoft.XLANGs.RuntimeTypes.dll" /reference:"C:\Program Files\Microsoft BizTalk Server 2009\Microsoft.BizTalk.Interop.Agent.dll" /reference:"C:\Program Files\Microsoft BizTalk Server 2009\Microsoft.BizTalk.Messaging.dll" /reference:"C:\Program Files\Microsoft BizTalk Server 2009\Microsoft.XLANGs.Engine.dll" /reference:"C:\Program Files\Microsoft BizTalk Server 2009\Microsoft.XLANGs.BizTalk.Engine.dll" /reference:"C:\Program Files\Common Files\Microsoft BizTalk\Microsoft.RuleEngine.dll" /reference:"C:\Program Files\Microsoft BizTalk Server 2009\Microsoft.XLANGs.BizTalk.ProcessInterface.dll" /reference:C:\Windows\Microsoft.NET\Framework\v4.0.21006\System.dll /reference:C:\Windows\Microsoft.NET\Framework\v4.0.21006\System.Xml.dll /reference:C:\Windows\Microsoft.NET\Framework\v4.0.21006\System.Data.dll /reference:C:\Windows\Microsoft.NET\Framework\v4.0.21006\System.Web.Services.dll /reference:"C:\Program Files\Common Files\Microsoft BizTalk\Microsoft.BizTalk.TOM.dll" /debug:pdbonly /keyfile:somekey.snk /optimize+ /out:obj\Release\TestSchemas.dll /target:library /warnaserror- Properties\AssemblyInfo.cs "C:\Builds\2\Test Project\Test Build\Sources\TestBizTalkApp\TestSchemas\SomeSchema.xsd.cs" "C:\Builds\2\Test Project\Test Build\Sources\TestBizTalkApp\TestSchemas\PropertySchema.xsd.cs"
CSC : warning CS1685: The predefined type 'System.Runtime.InteropServices.DefaultParameterValueAttribute' is defined in multiple assemblies in the global alias; using definition from 'c:\Windows\Microsoft.NET\Framework\v2.0.50727\System.dll' [C:\Builds\2\Test Project\Test Build\Sources\TestBizTalkApp\TestSchemas\TestSchemas.btproj]
PropertySchema.xsd.cs(64,35): error CS0433: The type 'System.Xml.XmlQualifiedName' exists in both 'c:\Windows\Microsoft.NET\Framework\v2.0.50727\System.XML.dll' and 'c:\Windows\Microsoft.NET\Framework\v4.0.21006\System.XML.dll' [C:\Builds\2\Test Project\Test Build\Sources\TestBizTalkApp\TestSchemas\TestSchemas.btproj]
PropertySchema.xsd.cs(72,36): error CS0433: The type 'System.Xml.XmlQualifiedName' exists in both 'c:\Windows\Microsoft.NET\Framework\v2.0.50727\System.XML.dll' and 'c:\Windows\Microsoft.NET\Framework\v4.0.21006\System.XML.dll' [C:\Builds\2\Test Project\Test Build\Sources\TestBizTalkApp\TestSchemas\TestSchemas.btproj]
Done Building Project "C:\Builds\2\Test Project\Test Build\Sources\TestBizTalkApp\TestSchemas\TestSchemas.btproj" (default targets) -- FAILED.
Done Building Project "C:\Builds\2\Test Project\Test Build\Sources\TestBizTalkApp\TestBizTalkApp.sln" (default targets) -- FAILED.
Done Building Project "C:\Builds\2\Test Project\Test Build\BuildType\TFSBuild.proj" (CompileSolution target(s)) -- FAILED.
Done Building Project "C:\Builds\2\Test Project\Test Build\BuildType\TFSBuild.proj" (CompileConfiguration target(s)) -- FAILED.
Done Building Project "C:\Builds\2\Test Project\Test Build\BuildType\TFSBuild.proj" (CoreCompile target(s)) -- FAILED.
Details (expand)

Product Language

English

Version

Team Foundation Server 2010 Beta 2

Operating System

Windows Server 2008

Operating System Language

English

Steps to Reproduce

1) Create an empty solution in VS 2008
2) Add new BizTalk project into the solution
3) Add simple BizTalk xml schema with promoted property.
4) Check in all source code into TFS 2010
5) Create new build definition for the solution from VS 2008 Team Explorer
6) Queue up new build on TFS 2010 build server

Actual Results

Compilation finishes with error:
PropertySchema.xsd.cs(64,35): error CS0433: The type 'System.Xml.XmlQualifiedName' exists in both 'c:\Windows\Microsoft.NET\Framework\v2.0.50727\System.XML.dll' and 'c:\Windows\Microsoft.NET\Framework\v4.0.21006\System.XML.dll'

Expected Results

Compilation success
      You can indicate your satisfaction with how Microsoft handled this issue by completing this quick 3 question survey. [Details]

 

File Attachments
0 attachments
Sign in to post a comment.
Posted by Microsoft on 6/21/2010 at 6:03 AM
The work-around will likely be required until the BizTalk team releases an update to their project system for VS 2010.
Posted by Nick Walker on 6/18/2010 at 7:03 PM
Is there official word/guidance on a fix for this? I'd be interested to know if a workaround is no longer needed.
Posted by AllanBenson2 on 5/21/2010 at 8:31 AM
Workaround worked for me. Make sure you also add a reference to system.Web.services
Posted by B. Huard i on 5/20/2010 at 1:54 PM
Possible workaround here: http://social.msdn.microsoft.com/Forums/en/msbuild/thread/acf1fc8d-8825-4188-9929-3cf384e4b7b4
Posted by Wes MacDonald on 5/5/2010 at 9:55 AM
We have this issue as well with the RTM release.
Posted by AllanBenson2 on 4/28/2010 at 4:23 AM
I had exactly the same error on both the TFS 2010 RC and RTM versions.
Posted by JarinK on 4/16/2010 at 8:57 AM
We have installed final release of TFS 2010 but we're getting the same error as in Beta 2 version, so no, the issue hasn't been resolved!
Posted by Microsoft on 2/3/2010 at 6:24 AM
We had a previous report around building BizTalk projects with TFS 2010 and I'm happy to say that it's been resolved for the release candidate. Thanks for reporting the issue.
Posted by Microsoft on 1/31/2010 at 5:55 PM
Thank you for your feedback, We are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.