I asked to use SonarQube to analyse the .NET Project. I installed sonarqube-5.6.7 and everything working fine as expected but the issue arise when I build the .net solution using MSBuild.SonarQube.Runner.exe. Solution is getting build successfully but getting error while sending report to Sonar server.
Please note, I am using Visual studio 2012 project with 4.5.2 framework, I don't use TFS and even Jenkins.
SonarQube.Scanner.MSBuild.exe begin /k:"key" /n:"Project name" /v:"1.0" - This step seems to work fine.
MSBuild.exe /t:Rebuild - This step seems to work fine.
SonarQube.Scanner.MSBuild.exe end - This step fails.
Output of the failing step:
D:\...>SonarQube.Scanner.MSBuild.exe end
SonarQube Scanner for MSBuild 3.1
Default properties file was found at C:\Users\xxxx\Downloads\sonarqube-5.6.7
\bin\SonarQube.Analysis.xml
Loading analysis properties from C:\Users\xxx\Downloads\sonarqube-5.6.7\bin
\SonarQube.Analysis.xml
Post-processing started.
The SonarQube MSBuild integration failed: SonarQube was unable to collect the re
quired information about your projects.
Possible causes:
1. The project has not been built - the project must be built in between the b
egin and end steps
2. An unsupported version of MSBuild has been used to build the project. Curre
ntly MSBuild 14.0 upwards are supported
3. The begin, build or end steps have not all been launched from the same fold
er
Generation of the sonar-properties file failed.
Unable to complete SonarQube analysis.
15:29:11.087 Creating a summary markdown file...
15:29:11.1 Post-processing failed. Exit code: 1
Can anyone let me know what I am missing?
As suggested below, I downloaded "sonar-scanner-msbuild-2.3.2.573.zip" and tried to rebuild the Visual Studio 2012 project which target framework version is 4.5.2 and got below errors. I tried to build with direct path of MSBuild 12 and also without giving the MSBuild full path but still getting the errors.
D:\test\test>C:\Users\xxxx\Downloads\sonarqube-5.6.7\bin\SonarQube.Scanner.M
SBuild.exe begin /k:"org.sonarqube:sonarqube-scanner-msbuild" /n:"Test Project"
/v:"1.0"
SonarQube Scanner for MSBuild 2.3.2
Default properties file was found at C:\Users\xxxx\Downloads\sonarqube-5.6.7
\bin\SonarQube.Analysis.xml
Loading analysis properties from C:\Users\xxxx\Downloads\sonarqube-5.6.7\bin
\SonarQube.Analysis.xml
Pre-processing started.
Preparing working directories...
11:23:11.818 Updating build integration targets...
11:23:11.863 Fetching analysis configuration settings...
11:23:13.712 Generating rulesets...
11:23:13.776 Provisioning analyzer assemblies for cs...
11:23:13.778 Installing required Roslyn analyzers...
11:23:13.992 Pre-processing succeeded.
D:\test\test>MSBuild.exe /t:Rebuild
Microsoft (R) Build Engine version 4.0.30319.34209
[Microsoft .NET Framework, version 4.0.30319.34209]
Copyright (C) Microsoft Corporation. All rights reserved.
Building the projects in this solution one at a time. To enable parallel build,
please add the "/m" switch.
Build started 09/10/2017 11:23:29.
Project "D:\test\test\test.sln" on node 1 (Rebuild target(s)).
ValidateSolutionConfiguration:
Building solution configuration "Debug|Any CPU".
Project "D:\test\test\test.sln" (1) is building "D:\test\test\test\test.csproj"
(2) on node 1 (Rebuild target(s)).
CoreClean:
Deleting file "D:\test\test\test\bin\test.dll".
Deleting file "D:\test\test\test\bin\test.pdb".
Deleting file "D:\test\test\test\obj\Debug\test.csprojResolveAssemblyReferenc
e.cache".
Deleting file "D:\test\test\test\obj\Debug\test.dll".
Deleting file "D:\test\test\test\obj\Debug\test.pdb".
GenerateTargetFrameworkMonikerAttribute:
Skipping target "GenerateTargetFrameworkMonikerAttribute" because all output fi
les are up-to-date with respect to the input files.
CoreCompile:
C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\Csc.exe /noconfig /nowarn:1701,
1702 /nostdlib+ /errorreport:prompt /warn:4 /define:DEBUG;TRACE /highentropyv
a+ /reference:"C:\Program Files (x86)\Reference Assemblies\Microsoft\Framewor
k\.NETFramework\v4.5.2\Microsoft.CSharp.dll" /reference:"C:\Program Files (x8
6)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5.2\mscorlib.dll
" /reference:"C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework
\.NETFramework\v4.5.2\System.ComponentModel.DataAnnotations.dll" /reference:"
C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework
\v4.5.2\System.Configuration.dll" /reference:"C:\Program Files (x86)\Referenc
e Assemblies\Microsoft\Framework\.NETFramework\v4.5.2\System.Core.dll" /refer
ence:"C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFra
mework\v4.5.2\System.Data.DataSetExtensions.dll" /reference:"C:\Program Files
(x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5.2\System.D
ata.dll" /reference:"C:\Program Files (x86)\Reference Assemblies\Microsoft\Fr
amework\.NETFramework\v4.5.2\System.dll" /reference:"C:\Program Files (x86)\R
eference Assemblies\Microsoft\Framework\.NETFramework\v4.5.2\System.Drawing.d
ll" /reference:"C:\Program Files (x86)\Reference Assemblies\Microsoft\Framewo
rk\.NETFramework\v4.5.2\System.EnterpriseServices.dll" /reference:"C:\Program
Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5.2\Sy
stem.Web.ApplicationServices.dll" /reference:"C:\Program Files (x86)\Referenc
e Assemblies\Microsoft\Framework\.NETFramework\v4.5.2\System.Web.dll" /refere
nce:"C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFram
ework\v4.5.2\System.Web.DynamicData.dll" /reference:"C:\Program Files (x86)\R
eference Assemblies\Microsoft\Framework\.NETFramework\v4.5.2\System.Web.Entit
y.dll" /reference:"C:\Program Files (x86)\Reference Assemblies\Microsoft\Fram
ework\.NETFramework\v4.5.2\System.Web.Extensions.dll" /reference:"C:\Program
Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5.2\Sys
tem.Web.Services.dll" /reference:"C:\Program Files (x86)\Reference Assemblies
\Microsoft\Framework\.NETFramework\v4.5.2\System.Xml.dll" /reference:"C:\Prog
ram Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5.2
\System.Xml.Linq.dll" /debug+ /debug:full /optimize- /out:obj\Debug\test.dll
/subsystemversion:6.00 /target:library /utf8output Properties\AssemblyInfo.cs
"C:\Users\xxxx\AppData\Local\Temp\.NETFramework,Version=v4.5.2.AssemblyA
ttributes.cs"
CopyFilesToOutputDirectory:
Copying file from "obj\Debug\test.dll" to "bin\test.dll".
test -> D:\test\test\test\bin\test.dll
Copying file from "obj\Debug\test.pdb" to "bin\test.pdb".
Done Building Project "D:\test\test\test\test.csproj" (Rebuild target(s)).
Done Building Project "D:\test\test\test.sln" (Rebuild target(s)).
Build succeeded.
0 Warning(s)
0 Error(s)
Time Elapsed 00:00:00.71
D:\test\test>C:\Users\xxxx\Downloads\sonarqube-5.6.7\bin\SonarQube.Scanner.M
SBuild.exe end
SonarQube Scanner for MSBuild 2.3.2
Default properties file was found at C:\Users\xxxx\Downloads\sonarqube-5.6.7
\bin\SonarQube.Analysis.xml
Loading analysis properties from C:\Users\xxxx\Downloads\sonarqube-5.6.7\bin
\SonarQube.Analysis.xml
Post-processing started.
The SonarQube MSBuild integration failed: SonarQube was unable to collect the re
quired information about your projects.
Possible causes:
1. The project has not been built - the project must be built in between the b
egin and end steps
2. An unsupported version of MSBuild has been used to build the project. Curre
ntly MSBuild 12.0 upwards are supported
3. The begin, build or end steps have not all been launched from the same fold
er
Generation of the sonar-properties file failed. Unable to complete SonarQube ana
lysis.
11:23:59.124 Creating a summary markdown file...
11:23:59.14 Post-processing failed. Exit code: 1
Starting from version 3.0, SonarQube Scanner for MSBuild requires MSBuild 14 or later to work.
It seems you have SonarQube Scanner for MSBuild 3.1,
but your project is build with Visual studio 2012,
which uses MSBuild 12.
You need to either:
Upgrade your Visual Studio project to 2015.
Use an older version of SonarQube Scanner for MSBuild (older than version 3.0)
Using an older version (2.3.2) you had a problem with the build step:
"C:\Program Files (x86)\MSBuild\12.0\Bin\"MSBuild.exe /t:Rebuild
This was required to work in order to be able to analyze.
According to your comment, the problem was resolved like so:
I have resolved this issue by updating C:\Program Files (x86)\MSBuild\12.0 folder with targets. I copy the target folder from MSBuild 4.0 to MSBuild 12.0 and it's working.
Related
I have a .NET 6 Windows Desktop app that I deploy with MSIX.
I can run and debug it on my own computer, but it fails to build with Azure Pipelines YAML.
I get the error:
C:\Program
Files\dotnet\sdk\6.0.101\Sdks\Microsoft.NET.Sdk\targets\Microsoft.PackageDependencyResolution.targets(267,5):
error NETSDK1047: Assets file 'D:\a\1\s\MyApp\obj\project.assets.json'
doesn't have a target for 'net6.0-windows10.0.19041.0/win-x64'. Ensure
that restore has run and that you have included
'net6.0-windows10.0.19041.0' in the TargetFrameworks for your project.
You may also need to include 'win-x64' in your project's
RuntimeIdentifiers.
App project file:
<TargetFramework>net6.0-windows10.0.19041.0</TargetFramework>
<RuntimeIdentifier>win10-x64</RuntimeIdentifier>
<Platforms>x64</Platforms>
Installer project file:
<TargetPlatformVersion>10.0.19041.0</TargetPlatformVersion>
<TargetPlatformMinVersion>10.0.19041.0</TargetPlatformMinVersion>
<TargetFramework>net6.0-windows10.0.19041.0</TargetFramework>
<RuntimeIdentifier>win10-x64</RuntimeIdentifier>
The pipeline task is VSBuild with Visual Studio 2022 (v. 17)
Nuget tool is version 6.0 installed with NugetToolInstaller task.
Azure Windows agent uses vmImage: 'windows-2022'
The error says:
Ensure that you have included 'net6.0-windows10.0.19041.0' in the
TargetFrameworks for your project. You may also need to include
'win-x64' in your project's RuntimeIdentifiers.
I have added 'net6.0-windows10.0.19041.0' in the TargetFramework for both the app and the installer projects.
If I replace win10-x64 with win-x64 it can build, but I need to use win10-x64 because one of the packages requires it (Microsoft.PowerShell.SDK with System.Management.Automation).
NEW:
After adding /p:RestoreLockedMode=true in the VS Build task, I now get the error:
MyApp.Installer.wapproj : error NU1004: The project MyApp has no
compatible target framework. The packages lock file is inconsistent
with the project dependencies so restore can't be run in locked mode.
Disable the RestoreLockedMode MSBuild property or pass an explicit
--force-evaluate option to run restore to update the lock file.
NEW NEW: I upgraded to .NET 7 but get the same error.
How do I fix the error?
Reproduction steps:
Stack: Windows 10, Visual Studio 2019 professional, BizTalk Server 2020 developer edition CU1.
In Visual Studio create a new Biztalk Server Project
Manage Nuget Package, Add a nuget package. pick one:
Known to break the build
autofac 6.0, 6.1, 6.2
nodatime 3.0.5
Azure.Storage.Blobs 12.9.1
Known to not break the build
autofac 5.2
many others I tested.
F6 (Build) or run msbuild
As far as my testing was going, whenever the nuget packages directly list a variant with a .net framework as a dependency, it works. Listing only .net standard and .net 5 as a dependency, as in the list above, fails the buil.
actual error:
PS C:\code\autofacRepro> msbuild
Microsoft (R) Build Engine version 16.11.0+0538acc04 for .NET Framework
Copyright (C) Microsoft Corporation. All rights reserved.
Building the projects in this solution one at a time. To enable parallel build, please add the "-m" switch.
Build started 8/24/2021 3:01:10 PM.
Project "C:\code\autofacRepro\autofacRepro.sln" on node 1 (default targets).
ValidateSolutionConfiguration:
Building solution configuration "Debug|Any CPU".
Project "C:\code\autofacRepro\autofacRepro.sln" (1) is building "C:\code\autofacRepro\autofacRepro.btproj" (2) on node 1 (default targets).
C:\Program Files (x86)\MSBuild\Microsoft\BizTalk\BizTalkCommon.targets(190,9): error MSB4018: The "AddBizTalkHiddenReferences" task failed unexpectedly. [C:\code\autofacRepro\autofacRepro.btproj]
C:\Program Files (x86)\MSBuild\Microsoft\BizTalk\BizTalkCommon.targets(190,9): error MSB4018: System.ArgumentException: String cannot have zero length. [C:\code\autofacRepro\autofacRepro.btproj]
C:\Program Files (x86)\MSBuild\Microsoft\BizTalk\BizTalkCommon.targets(190,9): error MSB4018: at System.Reflection.AssemblyName..ctor(String assemblyName) [C:\code\autofacRepro\autofacRepro.btproj]
C:\Program Files (x86)\MSBuild\Microsoft\BizTalk\BizTalkCommon.targets(190,9): error MSB4018: at Microsoft.VisualStudio.BizTalkProject.BuildTasks.AddBizTalkHiddenReferences.GetAssemblyNamesFromItems(ITaskItem[] items) [C:\co
de\autofacRepro\autofacRepro.btproj]
C:\Program Files (x86)\MSBuild\Microsoft\BizTalk\BizTalkCommon.targets(190,9): error MSB4018: at Microsoft.VisualStudio.BizTalkProject.BuildTasks.AddBizTalkHiddenReferences.Execute() [C:\code\autofacRepro\autofacRepro.btproj
]
C:\Program Files (x86)\MSBuild\Microsoft\BizTalk\BizTalkCommon.targets(190,9): error MSB4018: at Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute() [C:\code\autofacRepro\autofacRep
ro.btproj]
C:\Program Files (x86)\MSBuild\Microsoft\BizTalk\BizTalkCommon.targets(190,9): error MSB4018: at Microsoft.Build.BackEnd.TaskBuilder.<ExecuteInstantiatedTask>d__26.MoveNext() [C:\code\autofacRepro\autofacRepro.btproj]
Done Building Project "C:\code\autofacRepro\autofacRepro.btproj" (default targets) -- FAILED.
Done Building Project "C:\code\autofacRepro\autofacRepro.sln" (default targets) -- FAILED.
Build FAILED.
A repro zip package is available in this github issue. (at first I thougt, it was a special issue with autofac, but it is not)
My old stack (windows server 2016, visual studio 2015, biztalk 2016) is not affected. We are using autofac 6.1 in biztalk projects there without any issue.
I feel like this is a BizTalk bug but I am not smart enough to find the way Microsoft allows reporting it.
So finally the question is, is there a workaround or a bugfix?
I've had this with one of my own packages. This package was targeting .NET Standard 2.0. I had to add .NET Framework 4.8 (in my case) specifically as a target framework in the class library and recreate the package for it.
For public packages, you may want to create a PR or make a fork to include targeting of .NET Framework. Your BizTalk project then needs to reference the .NET Framework assembly rather than the .NET Standard one.
I get the following error when I try building my solution in a multi core build agents.
C:\Program Files (x86)\Microsoft Visual
Studio\2017\BuildTools\MSBuild\Microsoft\VisualStudio\v15.0\Web\Deploy\Microsoft.Web.Publishing.Deploy.FileSystem.targets(96,5):
error : Copying file obj\Release\Package\PackageTmp\bin\roslyn\csi.exe
to
C:\buildAgent\work\f7321f5187869991\Deploy_output\www\bin\roslyn\csi.exe
failed. The process cannot access the file
'C:\buildAgent\work\f7321f5187869991\Deploy_output\www\bin\roslyn\csi.exe'
because it is being used by another process.
[C:\buildAgent\work\f7321f5187869991\src\Feature\VersionPruner\code\Sitecore.Feature.VersionPruner.csproj]
The msbuild command I use to trigger the build is
"C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\MSBuild\15.0\bin\MSBuild.exe" ..\MySolution.sln "/target:Rebuild" /verbosity:minimal /toolsversion:15.0 /nologo /maxcpucount /p:Configuration=%1 /property:DeployOnBuild="true" /property:DeployDefaultTarget="WebPublish" /property:WebPublishMethod="FileSystem" /property:DeleteExistingFiles="false" /property:publishUrl="%cd%\_output\www" /property:_FindDependencies="false" /p:BuildSourceFolder="%cd%\..\src" /p:BuildOutputBaseFolder="%cd%\_output\configs" /property:BuildOutputWWWFolder="%cd%\_output\www"
The solution builds successfully when maxcpucount property is set to 1.
I'm going through some ASP.NET tutorials and I've encountered an error I don't know how to resolve. I just added a Bower pacakge(?) and Visual Studio (Enterprise 2015) placed it under a Dependencies branch. Under that is the Bower branch and in that the package appears. Both Dependencies and Bower say "- not installed" after them. I've right-clicked and selected the "Restore" option. Viusal Studio works for a while and then says an error occured. The following error appears in the Output window:
PATH=.\node_modules\.bin;C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\Extensions\Microsoft\Web Tools\External;%PATH%;C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\Extensions\Microsoft\Web Tools\External\git
"C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\Extensions\Microsoft\Web Tools\External\Bower.cmd" install --force-latest
bower underscore#~1.83 not-cached git://github.com/jashkenas/underscore.git#~1.83
bower underscore#~1.83 resolve git://github.com/jashkenas/underscore.git#~1.83
bower underscore#~1.83 ECMDERR Failed to execute "git ls-remote --tags --heads git://github.com/jashkenas/underscore.git", exit code of #-532462766
I'm not terribly familiar with Git, but I know I shouldn't have to have it installed in my workstation. Anyone know what's going on?
I believe bower uses Git client to pull packages directly from GitHub using entries in the packages bower.json file.
Specific to your problem, Git (and therefore bower) is unable to connect to GitHub due to firewall issues. Similar issue here
You can set global git variables (e.g. git config --global xxx) to set proxy etc. to hopefully work around this problem.
According to the error your Git Client is installed locally at C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\Extensions\Microsoft\Web Tools\External\git
I was wondering if anybody is using TFS 2010 beta 2 build server to build BizTalk 2009 projects created in VS 2008?
I created new BizTalk project in VS 2008 adding simple schema with promoted property. Then I created new build definition from VS 2008 Team Explorer and queued up new build on our TFS 2010 build server...
I'm getting compilation errors due to the conflicts in .NET Framework versions. Here is a snippet from compilation 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.
As you can see, there are references to the same assemblies for two different framework versions (2.0 and 4.0) which is causing conflicts.
Our setup is: Win2008 box with BizTalk 2009, VS 2008 SP1 and we installed TFS 2010 beta 2 build service on the same box and configured to run only as an build agent. Then we've got another Win2008 box with TFS 2010 beta 2 which is configured as a source control and build server with only a build controller set-up.
Any help on how to get rid of the references to framework 4.0 from build would be much appreciated. Thanks!
We installed final version of TFS 2010 but had the same issue with conflicting assemblies. It turns out there is a bug in BizTalk build task. Details and workaround can be found here.
I submitted a bug report to Microsoft and here is reply:
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.
I guess the only option now is to wait for RC and hope they really fixed that issue.