msbuild

问题 I'm trying to get an exec task inside an msbuild script to work and have found a very annoying issue. The exec command is sweet except that the process I'm running (Ncover.Console.exe) can't handle a backslash at the end of a directory name. To illustrate with a snipped example, the following works: <exec command="NCover.Console.exe nunit-console.exe some.dll [snip] //w c:\out" /> But this fails (note the slash at the end of "c:\out"): <exec command="NCover.Console.exe nunit-console.exe some

问题 When I run TFS 2013 with sonar I get the following error: No ProjectInfo.xml files were found. Check that the analysis targets are referenced by the MSBuild projects being built. Message: TF270015: 'SonarQube.MSBuild.Runner.exe' returned an unexpected exit code. Expected '0'; actual '1'. I use : sonarqube-5.1.zip sonar-csharp-plugin-4.0.jar SonarQube.MSBuild.Runner-0.9.zip sonar-runner-dist-2.4.zip I've followed instructions found in "SonarQube Installation Guide for Existing TFS Environment

问题 In Visual Studio when I linked a file from one project to the next, I get the following error when an attempt is made to load the linked resource. This only happens when the linked file is within a folder(s). Error: Message="'pack://application:,,,/projectName ;component/ResourceDictionary .xaml' value cannot be assigned to property 'Source' of object 'System.Windows.SharedResourceDictionary'. Example: Project1.Resources | |--> MergedResourceDictionary.xaml |--> ProjectResourceDictionary.xaml

问题 I'm currently trying to switch between a few different default Icons in a Visual C++ .rc file using #ifdef tags. The builds switching the #define value are being created through command line using MSBuild. The difficulty I have been running into is that using Visual Studio 2010, in order to pass a preprocessor definition to the resource compiler you must define it in the project settings (Config Properties -> Resources -> General). This makes it difficult to use an #ifdef tag because using

问题 I have a very odd issue, where I've created a custom MSBuild task that would move all files I need for my MVC project to a specific location so that we can publish it. This works fine when I trigger the script localy on my machine but as soon as I check this changes in and Teamcity runs the script, it copies everything except from the Bin folder. However, if run MSbuild directlly from the command line (same script), it does copy the bin folder. I don't understand why this isn't working when

问题 I have a very odd issue, where I've created a custom MSBuild task that would move all files I need for my MVC project to a specific location so that we can publish it. This works fine when I trigger the script localy on my machine but as soon as I check this changes in and Teamcity runs the script, it copies everything except from the Bin folder. However, if run MSbuild directlly from the command line (same script), it does copy the bin folder. I don't understand why this isn't working when

问题 I know Since the release of msbuild 15 (vs 2017) that NuGet is now fully integrated into MSBuild. I have a nuspec file with defining variables of package properties like: <metadata> <id>$id$</id> <version>$version$</version> <authors>$authors$</authors> ... </metadata> The nuspec file is located in the same folder of the project. When using nuget tool to create the package , it works fine. nuget pack When using msbuild v15, it raise an exception. run the command: msbuild -version Microsoft (R

问题 I know Since the release of msbuild 15 (vs 2017) that NuGet is now fully integrated into MSBuild. I have a nuspec file with defining variables of package properties like: <metadata> <id>$id$</id> <version>$version$</version> <authors>$authors$</authors> ... </metadata> The nuspec file is located in the same folder of the project. When using nuget tool to create the package , it works fine. nuget pack When using msbuild v15, it raise an exception. run the command: msbuild -version Microsoft (R

问题 I have installed the MSBuild (15.4.0) tools for Visual Studio 2017 on a build server. To do this I used the link entitled "Build Tools for Visual Studio 2017" from Visual Studio Downloads The path to the MSBuild.exe is: C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\MSBuild\15.0\Bin I have added this path to the Environment Variable 'path'. I have a powershell script with the following as the body for the build task: msbuild '..\MyApplication.sln' /t:Build /tv:15.0 /p

问题 I have a number of projects which are joined into a solution. Every project has it's own directory structure, and csproj files are located on diferrent level of folder structure. Every csproj has OutputPath property specified. OutputPath - is a relative path and it varies from project to project in such a way so all projects have the same output dir. It is work OK if I build a separate project. But everything changes if I try to build solution file. In this case every project output folder