msbuild

How can I prevent external MSBuild files from being cached (by Visual Studio) during a project build?

China☆狼群 提交于 2019-12-31 10:41:38
问题 I have a project in my solution which started life as a C# library project. It's got nothing of any interest in it in terms of code, it is merely used as a dependency in the other projects in my solution in order to ensure that it is built first. One of the side-effects of building this project is that a shared AssemblyInfo.cs is created which contains the version number in use by the other projects. I have done this by adding the following to the .csproj file: <ItemGroup> <None Include=

How to run nunit with msbuild from VS2010

折月煮酒 提交于 2019-12-31 10:24:50
问题 please tell me how to run nunit with msbuild. I am using TFS for code integration and VS2010 . 回答1: You probably want to integrate NUnit with TFSBuild and not MSBuild since you are using Team Foundation Server. You will need MSBuild tasks to be able to run NUnit as explained in the three following tutorials: Using NUnit and NCover with TFS Build Integrate Nunit test into a Tfs build MSBuild with NUnit The easiest way is to use the MSBuild Community Tasks where you already have a NUnit task

How to run nunit with msbuild from VS2010

假装没事ソ 提交于 2019-12-31 10:22:45
问题 please tell me how to run nunit with msbuild. I am using TFS for code integration and VS2010 . 回答1: You probably want to integrate NUnit with TFSBuild and not MSBuild since you are using Team Foundation Server. You will need MSBuild tasks to be able to run NUnit as explained in the three following tutorials: Using NUnit and NCover with TFS Build Integrate Nunit test into a Tfs build MSBuild with NUnit The easiest way is to use the MSBuild Community Tasks where you already have a NUnit task

Publish Web Deploy using VS Code

。_饼干妹妹 提交于 2019-12-31 09:19:56
问题 In Visual Studio, I use the "publish web" feature to do some web.config transforms, and publish a WebAPI project to our server. The publishing is done using Web Deploy. Now that I'm using Visual Studio Code, I've lost that tooling. But, I'd like to continue publishing the project using Web Deploy. Is there some way to write a VSCode task that will publish my project? Visual Studio Publish uses a [target].pubxml file. I have "staging.pubxml" and "production.xml". These look like MSBuild files.

Include referenced project's .config file

守給你的承諾、 提交于 2019-12-31 08:57:49
问题 Rather than excluding a file from the referenced output of an assembly, I want to add one! I have a console application project (BuildTest1) that references a second class library project (ClassLibrary1). The Visual Studio solution looks like this: I have a class library project that has an app.config. I want this .config file copied to the referring project's output, just like the .dll and .pdb files are. The config file for the class library is copied to the class library output directory

How to build using MSBuild and Delphi XE2

橙三吉。 提交于 2019-12-31 08:54:50
问题 I've been building projects using Delphi XE and MSBuild using the following simple example which works fine in a batch file. Project1 is an empty project created using 'File | New | VCL forms application in the IDE: call "c:\Program Files (x86)\Embarcadero\RAD Studio\8.0\bin\rsvars.bat" msbuild.exe /target:Build /p:config=Release "c:\scratch\test\project1.dproj" pause If I created a new empty project in Delphi XE2, save it as project1.dproj (the dproj is VERY different from XE) and run the

Path to SignTool.exe or “Windows Kits” directory when using Visual Studio 2012

人走茶凉 提交于 2019-12-31 08:24:12
问题 How do you get the path to SignTool.exe when using Visual Studio 2012? In Visual Studio 2010, you could use <Exec Command=""$(FrameworkSDKDir)bin\signtool.exe" sign /p ... /> Where $(FrameworkSDKDir) is "c:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Bin\" But in Visual Studio 2012, $(FrameworkSDKDir) is "C:\Program Files (x86)\Microsoft SDKs\Windows\v8.0A\bin\" and SignTool is in "c:\Program Files (x86)\Windows Kits\8.0\bin\x64\" Is there a way of getting the path to this directory

Visual Studio prebuild powershell script exiting with code 9009 and failing to build

和自甴很熟 提交于 2019-12-31 05:42:07
问题 In my project I have set pre-build event that updates content of *.cs and *.xaml files (which are included in project being built). I use Set-Content Powershell command for it. When I test it in Powershell console everything is working perfectly. But when I paste as in pre-build event it generates error with code 9009 and prevents VS from successfully building my project. I have set build output verbosity to Diagnostic , but there's no more information on it. What could be the problem? My

How to set PlatformToolset property from MSbuild?

霸气de小男生 提交于 2019-12-31 05:33:04
问题 We are experiencing AppVeyor x64 build failures, and trying a suggestion to set PlatformToolset to DefaultPlatformToolset. The property value is undocumented, so we want to thoroughly test it. We wired DefaultPlatformToolset into our AppVeyor configuration file: test_script: - cmd: >- msbuild /t:Build /p:PlatformToolset=DefaultPlatformToolset cryptlib.vcxproj msbuild /t:Build /p:PlatformToolset=DefaultPlatformToolset cryptest.vcxproj msbuild /t:CopyCryptestToRoot /p:PlatformToolset

MSBuild. Create EmbeddedResource before build

五迷三道 提交于 2019-12-31 04:46:06
问题 I want to embed local references in the assembly before compiling the main unit. But the written target does not work. <Target Name="EmbedLocal" BeforeTargets="CoreCompile"> <Message Text="Run EmbedLocal for $(MSBuildProjectFullPath)..." Importance="high"/> <ItemGroup> <EmbeddedResource Include="@( ReferencePath->WithMetadataValue( 'CopyLocal', 'true' )->Metadata( 'FullPath' ) )"/> </ItemGroup> <Message Text="Embed local references complete for $(OutputPath)$(TargetFileName)." Importance=