msbuild

问题 I'm trying to read the AssemblyInformationalVersion from the AssemblyInfo file with msbuild but I am failing so far. The below one gets me the digits but I need to whole input inside quotes: <PropertyGroup> <Pattern>\[assembly: AssemblyInformationalVersion\(.(\d+)\.(\d+)\.(\d+)</Pattern> <In>@(ItemsFromFile)</In> <Out>$([System.Text.RegularExpressions.Regex]::Match($(In), $(Pattern)))</Out> </PropertyGroup> <Message Text="Output : $(Out.Remove(0, 41))"/> This is the target line for example:

问题 I have a primary build file that is managed through source control. It contains a project <Import> that adds a project that contains settings unique to the local environment. I want to add a temporary project to my copy of the local project file, so I have the following. Primary Build File: <Project> <Import Project="LocalOptions.xml" /> <ItemGroup> <CatalogProject Include="$(SolutionRoot)\MainProject\MainProject.vbproj"/> </ItemGroup> </Project> Local Project File: <Project> <ItemGroup>

问题 I'm translating a GNU Makefile into MSBuild XML. I have the following sed command (part of a larger command): ... | sed 's/^Q(.*)/"&"/' | ... When I execute just that sed portion in Cygwin , it "works" in the sense that it doesn't error out. However, after I've translated it to MSBuild XML - replaced the XML-sensitive symbols with " , & , &apos; - I get the error sed: unsupported command ' I'm sure it's not an issue with XML escaping issues; the Visual Studio build log says Task Parameter

问题 I cannot see why the below build is failing. The project builds successfully. What could "##[error]Unexpected exit code received from msbuild.exe: 1" result from in the below output? Executing the powershell script: C:\LR\MMS\Services\Mms\TaskAgentProvisioner\Tools\tasks\VSBuild\1.0.13\VSBuild.ps1 C:\Program Files (x86)\MSBuild\14.0\bin\msbuild.exe "C:\a\8ac4a4f6\Root\src\MyProject.Api\MyProject.Api.xproj" /nologo /m /nr:false /fl /flp:"logfile=C:\a\8ac4a4f6\Root\src\MyProject.Api\MyProject

问题 I'm creating a Visual Studio Package (vsix) (shameless plug: pMixins ) and I want to build the vsix package using the TeamCity continuous integration server. TeamCity uses MSBuild in the background. I am comfortable installing the Visual Studio SDK on my build agent, but I do not want to install a full version of Visual Studio. When I run the Visual Studio SDK installer, it complains that Visual Studio isn't present. How can I use MSBuild (via TeamCity) to build my vsix without having to

问题 Does anyone know what causes this error? I'm having trouble finding any information on it. 来源： https://stackoverflow.com/questions/7418476/msbuild-error-refcount-should-not-be-less-than-1

问题 NuGet apparently has some logic to determine what MSBuild Executable to use. Is there a way to override this behavior? Or at least a way to tell it to use the x86 MSBuild instead of x64? MSBuild auto-detection: using msbuild version '14.0' from 'C:\Program Files (x86)\MSBuild\14.0\bin\amd64'. 回答1: From the command-line documentation, you can specify -MSBuildPath or -MSBuildVersion on the command line. MSBuildPath (4.0+) Specifies the path of MSBuild to use with the command, taking precedence

问题 We are chasing an issue never seen before in many years of .net development: MSBUILD : error MSB4166: Child node "5" exited prematurely. Shutting down. Diagnostic information may be found in files in the temporary files directory named MSBuild_*.failure.txt. We have no idea what is going on. This build machine has been in service for months, and runs builds under a CI system. The question is: What dir do I look in for the diag files? I searched the whole system for msbuild*.txt , and find

问题 This is not a runtime error but a build error in the following configuration Windows 10 version 1511,(swedish) Visual studio 2015 Community update 3 Cordova tools for Visual studio version 6.1.1 AngularJs 1.5.8 The error only arises when trying to build for 'Windows AnyCPU' or Windows Phone universal not for the other platforms.I suspect that it is the angular object which is undefined but I'm not sure of this. The only information is Line 1 and Col 1 but not in what file. 回答1: Because I

问题 I have a C# Visual Studio project (.csproj) that has a reference to the Framework64 version of System.Data . When I try to build using MSBuild/Team Foundation Server (TFS) on another machine, it fails as the 64-bit DLL doesn't exist. Should I bind to the Framework version, or will this limit me when running on 64-bit machines? Does .NET redirect the binding to use 64-bit when possible? 回答1: I think you mean Any CPU in your question, correct? Assuming that's the case, binding without regard