Hi,

We have defined several configurations on *.csproj files in order to compile code for .NET v3.5 and v4.0. We use msbuild conditions to achieve that with the msbuild elementTargetFrameworkVersion. For the configurations that we want to compile for v3.5  we use the element<TargetFrameworkVersion>v3.5</TargetFrameworkVersion> and for v4.0 we use the same element with value v4.0. Here's a example of what we are talking about:

<PropertyGroup Condition="'$(Configuration)|$(Platform)' == 'Debug v4.0|AnyCPU'"><TargetFrameworkVersion>v4.0</TargetFrameworkVersion><DefineConstants>NET40=True,NET4X=True</DefineConstants>
	...</PropertyGroup>

Calling the msbuild from the command line with the right configurations (for instance "Debug v4.0"), we are able to compile code for v3.5 or v4.0. We are not able to achieve that on Visual Studio 2013 Premium. Whenever we change the configuration on the "Configuration Manager", the target framework used is always v3.5, even if we select a configuration that explicitly defines the v4.0 framework version (for instance "Debug v4.0").

We have tried to change many things on the *.csproj XML elements without success.

Is there a way to allow multitargeting compilation on Visual Studio 2013 Premium by only changing the configuration from the "Configuration Manager" and not having explicitly change the target framework directly from the project settings? We have a big number of projects to be compiled with multitargeting.

We can find & replace the msbuild TargetFrameworkVersion element of the genericmsbuildPropertyGroup element, the one without any msbuild condition (it seems like Visual Studio looks to that element in order to know the target framework version and does not takes in account the ones defined for the specific configurations), but then we must take special attention when committing files to the source code repository.

Best Regards,
BdaF

I am getting the following error while using MSBuild: "error CS1606: Assembly signing failed; output may not be signed -- The process cannot access the file because it is being used by another process." This error sometimes occurs and sometimes doesn't while performing a build on the same code base. It also sometimes occurs and sometimes doesn't while using the underlying MS-DOS command. However, it does NOT occur while compiling within VS2005.  It also appears to be the SAME assembly.  Any ideas?

MSBuild Output:

Target MasterBuildAndDeploy:
        Target ActualBuild:
            "C:\Program Files\Microsoft Visual Studio 8\Common7\Tools\..\IDE\devenv.exe" C:\Development\Workspaces\saugust\Endurance.Insurance.IITP\main\BuildScripts\..\\Endurance.ESB.sln /Build Debug /Out "C:\Development\Workspaces\saugust\Endurance.Insurance.IITP\main\BuildScripts\..\\Logs\Endurance.ESB.sln.log"
            C:\Development\Workspaces\saugust\Endurance.Insurance.IITP\main\BuildScripts\Endurance.ESB.MGA.Build.Common.Targets(98,3): error MSB3073: The command ""C:\Program Files\Microsoft Visual Studio 8\Common7\Tools\..\IDE\devenv.exe" C:\Development\Workspaces\saugust\Endurance.Insurance.IITP\main\BuildScripts\..\\Endurance.ESB.sln /Build Debug /Out "C:\Development\Workspaces\saugust\Endurance.Insurance.IITP\main\BuildScripts\..\\Logs\Endurance.ESB.sln.log"" exited with code 1.
        Done building target "ActualBuild" in project "Endurance.ESB.MGA.Build.General.proj" -- FAILED.
    Done building target "MasterBuildAndDeploy" in project "Endurance.ESB.MGA.Build.General.proj" -- FAILED.

VS Output:

------ Build started: Project: Endurance.ESB.Schemas, Configuration: Development .NET ------
Updating references...
Performing main compilation...
C:\Development\Workspaces\saugust\Endurance.Insurance.IITP\main\Endurance.ESB.Common\Endurance.ESB.Schemas\MGA_Policy_Request_Envelope.xsd: warning BEC1006: Node "<Schema>" - The distinguished field 'IsValidated' might not exist in the schema.
C:\Development\Workspaces\saugust\Endurance.Insurance.IITP\main\Endurance.ESB.Common\Endurance.ESB.Schemas\MGA_Policy_Request_XML.xsd: warning BEC1002: Node "EndorsementNumber" - Data type of this field or simple content record (xs:int) and the promoted property 'ns0:EndorsementNo' (xs:string) should be the same or they should map to the same CLR Type.
C:\Development\Workspaces\saugust\Endurance.Insurance.IITP\main\Endurance.ESB.Common\Endurance.ESB.Schemas\MGA_Policy_Request_XML.xsd: warning BEC1002: Node "EndorsementNumber" - Data type of this field or simple content record (xs:int) and the promoted property 'ns0:EndorsementNumber' (xs:string) should be the same or they should map to the same CLR Type.
C:\Development\Workspaces\saugust\Endurance.Insurance.IITP\main\Endurance.ESB.Common\Endurance.ESB.Schemas\MGA_Policy_Request_XML.xsd: warning BEC1005: Node "<Schema>" - The promoted field or simple content record 'ns1:IsValidated' might not exist in the schema.
C:\Development\Workspaces\saugust\Endurance.Insurance.IITP\main\Endurance.ESB.Common\Endurance.ESB.Schemas\PolicyTransactionsBatch.xsd: warning BEC1008: Node "PolicyTransactionsBatch" - Body XPath property is invalid or references a node that may not exist in the schema.
c:\Development\Workspaces\saugust\Endurance.Insurance.IITP\main\Endurance.ESB.Common\Endurance.ESB.Schemas\AssemblyInfo.cs(21,12): warning CS1699: Use command line option '/keyfile' or appropriate project settings instead of 'System.Reflection.AssemblyKeyFile'
error CS1606: Assembly signing failed; output may not be signed -- The process cannot access the file because it is being used by another process. 

Build complete -- 1 errors, 6 warnings 

Shawn (Mail@ShawnAugust.Com)

Trying to do an incremental product build using DEVENV at the command prompt from a .bat file. We have 500+ Solutions that end up creating 1300+ dll's and exe's. What I am seeing is projects rebuilding when they should not be as no changes have been made. I clear my BIN folder and do a complete build of solutions using the /build directive against each .sln file. Once all the files build. I do it again and I get a number of files rebuilding for no reason other than they all say:

Output file "__NonExistentSubDir__\__NonExistentFile__" does not exist

This doesn't really help me as it is not pointing to what is not found. Also, if I do the build on 5/6/2015 and then on the morning of 5/7/2015 I just start up the /build flavor of the batch process, all the files are rebuilding with the same output file message.

Our client wants to automate the build (common task like pull code out of source control, build code, copy to deployment folder etc...) for multiple projects. It is currently manul process.Some projects are in Vb5/ Vb6, some projects are written in .net and some projects using both VB6 &.net. They are using VSS and SVN (subversion) as a source repository. They want to use Msbuild to automate the build for all these projects. I have few questions regarding this

1. Is it possible to automate VB5, VB6 projects using MSbuild ?
2. Do we need to write separate Msbuild script for each and every project or Is there any way we can simplify this process of automating in above scenario – multiple programming language, different source control?

Any help/suggestion on this is greatly appreciated. Thanks in advance!

Hi All,

Acquiring two audio input channel in single PC parallely.

I am able to acquire one audio input channel using MCI API functions, which audio card is configured as "Default Device".

I am not able to acquire second audio input channel of audio card configured as "Default Communication Device", So can anybody guide me how to acquire  audio card configured as "Default Communication Device" as well as audio card is configured as "Default Device" parallely

hi.

I have a solution with (~100 projects, c#/c++/cli) multiple configurations (debug32/release32/debug64/release64). When I change one c# source file in one of the projects and press "build", vs builds the assembly that file belongs to as well as all projects that are dependent on that assembly. That is what I would expect.

(Note: Before that single change, all configurations have been completely rebuild.)

When I next change to a different configuration and press build, vs rebuilds everything (as if "rebuild all" was pressed). Obviously it should also only build the single changed assembly and the dependent projects. Any ideas of what might be causing this?

WM_THX
-thomas woelfer

http://www.die.de/blog

I have a solution that I can build from Visual Studio. Configuration manager is set to build "QL Release | Win32".   I saved all after building in Visual Studio 2013.

I tried a command line build:

"C:\Program Files (x86)\MSBuild\12.0\Bin\MSBuild.exe" /nologo /p:Configuration="QL Release" /verbosity:detailed /t:Rebuild /fileloggerparameters:LogFile="d:\myProduct\windows_build_logs\QL_out.txt"  "d:\myProduct\mySolution\QL.sln"

The logfile references a non-existent ".metaproj" file:

Build started 5/7/2015 5:31:04 PM.
Project "d:\myProduct\mySolution\QL.sln" on node 1 (Rebuild target(s)).
Building with tools version "2.0".
Target "ValidateSolutionConfiguration" in file "d:\myProduct\mySolution\QL.sln.metaproj" from project "d:\myProduct\mySolution\QL.sln" (entry point):
Using "Error" task from assembly "Microsoft.Build.Tasks.v12.0, Version=12.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a".
Task "Error"
d:\myProduct\mySolution\QL.sln.metaproj : error MSB4126: The specified solution configuration "QL Release|X64" is invalid. Please specify a valid solution configuration using the Configuration and Platform properties (e.g. MSBuild.exe Solution.sln /p:Configuration=Debug /p:Platform="Any CPU") or leave those properties blank to use the default solution configuration. [d:\myProduct\mySolution\QL.sln]
Done executing task "Error" -- FAILED.
Done building target "ValidateSolutionConfiguration" in project QL.sln" -- FAILED.
Done Building Project "d:\myProduct\mySolution\QL.sln" (Rebuild target(s)) -- FAILED.


Build FAILED.

"d:\myProduct\mySolution\QL.sln" (Rebuild target) (1) ->
(ValidateSolutionConfiguration target) -> 
  d:\myProduct\mySolution\QL.sln.metaproj : error MSB4126: The specified solution configuration "QL Release|X64" is invalid. Please specify a valid solution configuration using the Configuration and Platform properties (e.g. MSBuild.exe Solution.sln /p:Configuration=Debug /p:Platform="Any CPU") or leave those properties blank to use the default solution configuration. [d:\myProduct\mySolution\QL.sln]

    0 Warning(s)
    1 Error(s)

Time Elapsed 00:00:00.06

I don't know where it is getting the ".metaproj" file as there isn't one.  I've done a clean, even removed the QL.sdf and QL.v12.suo files, but the command line build still wants to build a non-existent configuration.  That configuration most likely came from some experimental work which has since been removed. The solution contains 10 projects.  None of the project or solution files reference x64 so I can't tell where MSBUILD is getting this information.

Message: Publishing to 'C:\BuildMaster\_SVCTMP\_A3\\Azure\'

Message: TargetServiceDefinition is C:\BuildMaster\_SVCTMP\_A3\_S7\WRK\ServiceDefinition.csdef

Message: TargetServiceConfiguration is C:\BuildMaster\_SVCTMP\_A3\_S7\WRK\ServiceConfiguration.cscfg

Message: Roles is C:\BuildMaster\_SVCTMP\_A3\Src\SimpleTixPlatformService\SimpleTixPlatformService\obj\Production\StPlatformWebRole\;C:\BuildMaster\_SVCTMP\_A3\Src\SimpleTixPlatformService\SimpleTixPlatformService\obj\Production\StMaintenanceWorkerRole\

C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v12.0\Windows Azure Tools\2.6\Microsoft.WindowsAzure.targets(3003,5): error MSB4018: The "CSPack" task failed unexpectedly.

Done building project "SimpleTixPlatformService.ccproj" -- FAILED.

System.Runtime.Remoting.RemotingException: Object '/d89f1fb8_a98c_41a6_9c53_1b8f2557e719/qm9s7i5e0gyzgtaxrixmsjp0_294.rem' has been disconnected or does not exist at the server.

Building Project "CommonClassLib.csproj" (Publish target(s)):

at System.IO.FileStream.get_CanRead()

Message: Skipping unpublishable project.

at MS.Internal.IO.Zip.ZipIOLocalFileBlock.CheckFileAccessParameter(Stream stream, FileAccess access)

Done building project "CommonClassLib.csproj".

at MS.Internal.IO.Zip.ZipIOLocalFileBlock.GetStream(FileMode mode, FileAccess access)

Building Project "SimpleTickReporting.csproj" (Publish target(s)):

at System.IO.Packaging.ZipPackagePart.GetStreamCore(FileMode mode, FileAccess access)

Message: Skipping unpublishable project.

at System.IO.Packaging.PackagePart.GetStream(FileMode mode, FileAccess access)

Done building project "SimpleTickReporting.csproj".

at Microsoft.ServiceHosting.Tools.Packaging.Utils.CopyFullStreamToPart(Stream source, PackagePart part, PackageManifest manifest)

Building Project "USAePayService.csproj" (Publish target(s)):

at Microsoft.ServiceHosting.Tools.Packaging.PackageCreator.CreateRolePackages(ModelProcessor modelProcessor, PackageManifest applicationManifest, Package applicationPackage)

Message: Skipping unpublishable project.

at Microsoft.ServiceHosting.Tools.Packaging.PackageCreator.CreatePackage(Stream outputStream, Action`1 postProcess, PackageRestrictions restrictions)

Done building project "USAePayService.csproj".

at Microsoft.ServiceHosting.Tools.Packaging.ServiceApplicationPackage.CreateServiceApplicationPackage(String serviceModelFileName, String serviceDescriptionFile, Stream output, IPackageSecurity encrypt, IDictionary`2 namedStreamCollection, String userInfo, EventHandler`1 rolePackagePartAddedHandler)

Building Project "CommonClassLib.Test.csproj" (Publish target(s)):

at Microsoft.ServiceHosting.Tools.MSBuildTasks.PackageCreator.CreateServiceApplicationPackage(String serviceRdFilePath, String processedServiceDefinitionFile, FileStream packageStream, IDictionary`2 namedStreams, Dictionary`2 rolesDictionary)

MakeDir: Creating directory "obj\Release\".

at Microsoft.ServiceHosting.Tools.MSBuildTasks.PackageCreator.CreateServiceApplicationPackage(String serviceRdFilePath, String processedServiceDefinitionFile, FileStream packageStream, IDictionary`2 namedStreams, Dictionary`2 rolesDictionary)

Building Project "CommonClassLib.csproj" (default targets):

at Microsoft.ServiceHosting.Tools.MSBuildTasks.CSPack.TryCreatePackage(ServiceDefinitionModel sm)

Done building project "CommonClassLib.csproj".

at Microsoft.ServiceHosting.Tools.MSBuildTasks.CSPack.Execute()

Building Project "StMaintenanceWorkerRole.csproj" (default targets):

at Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute()

Done building project "StMaintenanceWorkerRole.csproj".

at Microsoft.Build.BackEnd.TaskBuilder.<ExecuteInstantiatedTask>d__20.MoveNext()

Building Project "CommonClassLib.csproj" (GetNativeManifest target(s)):

Done building project "CommonClassLib.csproj".

Building Project "StMaintenanceWorkerRole.csproj" (GetNativeManifest target(s)):

Done building project "StMaintenanceWorkerRole.csproj".

MSBuild: Skipping target "GenerateTargetFrameworkMonikerAttribute" because all output files are up-to-date with respect to the input files.

I installed Windows 10 Tech Preview (10074) and Visual Studio 2015 RC, and am trying to build my solution (which was previously built with Visual Studio 2013)

If I build in VS, everything builds successfully, however when I use MSBuild I get this error on a handful of projects (not all of them)

C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets(2428,5): error MSB3086: Task could not find "LC.exe" using the SdkToolsPath "" or the registry key "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SDKs\Windows\v8.0A\WinSDK-NetFx40Tools-x86".
Make sure the SdkToolsPath is set and the tool exists in the correct processor specific location under the SdkToolsPath and that the Microsoft Windows SDK is installed.

This doesn't exist on Windows 10, how do I update this to use the current Windows SDK? What is 8.0a? Is that coming from Visual Studio 2013? Why should I have to install that, too? Very confused.

Thanks!

I created an SSDT database solution in VS 2012. I installed VS 2013 and opened the solution and the local build fails. If I close VS 2013 and reopen VS 2012 and build the solution, the build is successful. Both VS versions are reading from the same solution folder mapped to a TFS team project. I have tried forcing the latest version with all overwrite options and receive the same result.

Microsoft Visual Studio Ultimate 2013
Version 12.0.31101.00 Update 4
Microsoft .NET Framework
Version 4.5.51209

Installed Version: Ultimate

VS 2013 output:

VS 2012 output:

Hi there -

is there ANY way to turn off msbuild warnings (e.g. MSB3305)?

09:50:17.900    29>C:\Program Files (x86)\MSBuild\12.0\bin\amd64\Microsoft.Common.CurrentVersion.targets(2234,5): warning MSB3305: Processing COM reference "" from path "C:\Windows\System32\stdole2.tlb". The type library importer could not convert the signature for the member 'DISPPARAMS.rgvarg'. [C:\Builds\1\BINARY\Tool_CI\src\Tool\Apps\Platform\Platform.csproj]

We'd like to establish a 0 warnings policy for our project - and not set the warning level to0 - but cannot get rid of the mentioned warning on our build server.

Any suggestions much appreciated!

Thanks,
Jay

Hi,

For quite some time now we've had incremental build problems in our VS2010 project, where changes to a header were not causing items including that header to recompile (visual studio was not calculating dependencies correctly). Since we were upgrading to VS2013 soon, I thought maybe the problem would have been fixed, only to discover the problem was still there in VS2013. At the most basic level, I could do a rebuild all, then delete the contents of one header entirely, do an incremental build, and only one of perhaps six .cpp files including that header, would actually detect the header change and attempt to compile.

Looking at C1.read.1.tlog, many of the cpp files were missing .h dependencies that should be there, after a rebuild. To confuse matters, after a rebuild, if I then force compile of an individual .cpp , the C1.read.1.tlog will now show the correct set of dependencies for that file. So it only affected some files, and only when doing a project build (not when forcing an individual .cpp to compile).

I finally noticed in my .tlog there was a header file with a ^ prefix. I realized this header had been configured incorrectly, to have "Item Type" set to "C/C++ compiler", instead of "C/C++ header". Strangely, that header contained no other headers, only a simple one line forward declaration. Yet the dependencies listed for that header in the .tlog, were quite extensive, which made no sense at all.

Changing this header file to "C/C++ header" fixed the dependency problem. The C1.read.1.tlog, after a rebuild all, went from about 13MB in size, to around 42MB (reflecting all the missing dependencies that were now present).

I'm posting this as a discussion to make this information public to other users possibly experiencing this problem. It was a real headache to track down, and collectively wasted countless days, perhaps weeks of dev time, due to heisenbugs and mystery linker errors resulting from it.

To reproduce the issue, create a new visual studio project dummy project (with say Sample.cpp), add in some empty header files

"SomeHeaderFile.h"

"DependencyBreaker.h"

Then add the following to Sample.cpp

#include "DependencyBreaker.h"
#include "SomeHeaderFile.h"

Mark "DependencyBreaker.h" as "C/C+ compiler". Rebuild the project. Open C1.read.1.tlog.

Note the file content has DependencyBreaker.h listed as having a dependency, even though it doesn't include anything.

^..\CONSOLEAPPLICATION1\DEPENDENCYBREAKER.H
..\CONSOLEAPPLICATION1\CONSOLEAPPLICATION1\SOMEHEADERFILE.H

Note that Sample.cpp does not have any dependency information for the included headers. If you then force compile of Sample.cpp file in isolation, the correct dependency information will now appear in the .tlog.

If you reverse the order Sample.cpp as follows, the dependency information will correctly show "SomeHeaderFile.h", but not "DependencyBreaker.h". Additionally "DependencyBreaker.h" will have no dependencies (as expected).

If you mark the DependencyBreaker.h as "C/C++ header", then the .tlog always shows the correct dependency information, regardless of rebuild all, or individually compiling the file.

Anyway I hope this information will be of use to anyone else who might have run into this issue.

Hi

I am using visual studio 2013 professional. while building  a simple windows or web project I am facing following issues

1. If there is any error in build, I don't see that error in error list

2.Build fails with error : CSC.exe exited with error code 1

I have Net framework 4.5.1 installed on my machine.

Please provide some solution for this issue.

Thanks

I've created a series of build definitions in the Team Explorer of Visual studio for CI and manual deployment.   The definitions additional deploy to Azure site.  All works fine. 

what i would like to do is be able to run in the command like a bat file that will trigger ALL the build definitions to run.  (such to deploy to TEST / Production when needed). 

How can i do that?     

I have a situation where I have migrated a fairly large solution from VSS and VS2010 to TFS and VS2013. After using the migration tool and getting the solution from the TFS source control into VS 2013, I was able to successfully build within VS.  However, when I attempt to have the build server build the solution, it always fails using a build definition that starts with a clean workspace.  If I create a definition that does not use a clean workspace, it will build unsuccessfully the first time but will succeed on subsequent runs every time. 

The errors that are produced are always one of these 3--not consistently:

/localhost_57369/....../Forms/Search.aspx (1): Object reference not set to an instance of an object.

/localhost_57369/....../Forms/AdvancedSearch.aspx (1): Object reference not set to an instance of an object.

/localhost_57369/....../Forms/BasicSearch.aspx (1): Object reference not set to an instance of an object.

The first line in each of these files starts with <%@ Page Title=".........   MasterPageFile="~/...../Search.master" ..... %>  (sanitized with ....s)

Has anyone experienced a scenario similar to this?

Hello there,

My Visual Studio has recently been having problems in which when I build my application (Run without debugging) Visual Studio opens about 200 processes and the build fails.

These processes do not disappear, which causes slowdowns as each takes up about 3-4MB of memory.

The processes are mostly MSBuild.exe, and I believe conhost.exe.

Thank you