msbuild

问题 I need to add certificate signing to my build. Below is a sample of the working script I wrote, however it includes the password to the .pfx file. I can't keep the password in the build script. What are "best practices" or hacks that you would use in this type of situation? <ItemGroup Label="SignFiles"> <SignFilesInclude="$(FileLocation)\**\*.exe"/> </ItemGroup> <Exec Command="$(SignTool) sign /v /ac C:\MSCV-VSClass3.cer /f C:\Certificate.pfx /p Password /t http://timestamp.verisign.com

问题 I'm trying to get MSBuild 2010 to publish a web app to a specific location. I can get it to publish the deployment package to a particular path, but the deployment package then adds its own path that changes. For example: if I tell it to publish to C:\dev\build\Output\Debug then the actual web files end up at C:\dev\build\Output\Debug\Archive\Content\C_C\code\app\Source\ControllersViews\obj\Debug\Package\PackageTmp And the C_C part of the path changes (not sure how it chooses this part of the

问题 In my MSBuild script I need to pass the full directory as a parameter. How can I get it? Example: I am running the script from C:\dev, and I want a relative path temp, so I am after C:\dev\temp. Note: I don't know from which folder the script will be run. 回答1: Igor is pretty close. MSBuildProjectDirectory is the property that will give you the full path to the project file which was invoked on the command line. So if you have the following scripts: C:\temp\MyProj.proj C:\shared\shared.targets

问题 When I'm running the test in Microsoft Test Manager I get an error: The build directory of the test run either does not exist or access permission is required. What does it mean? Where can I check build directory? 回答1: I suppose you are running automated tests. If you are running automated test in Microsoft Test Manageg (MTM) you have Test Case(s) automated by your test implementation. So MTM need to know where is the drop location of the build building your tests. That means you have to:

问题 Web essentials works great when build in VS, but seems no way to build/bundle (Scss/js,Html,Sprit) when call MSBuild (like team city). I googled lot stuffs, but only find - https://www.nuget.org/packages/Pta.Build.WebEssentialsBundleTask/ but it only support bundle, is there any other way to do that ? 回答1: finally, I found http://madskristensen.net/, Mads Kristensen split Bundler & Minifier and Web Compiler from Web Essentials 2015, and it supported integrate with MSBuild process !!!! https:/

问题 I've decided to try PhoneGap and installed the Node package for it. (Phonegap 3.3.0) Android projects work fine. But when I try to build a WP8 (or WP7) App I get this error: An error occurred while building the wp7 project.ERROR: MSBuild failed to create .xap when building cordova-wp7 for debugging. I'm running Windows 8 Pro 64 bit, Visual Studio 2013 Ultimate, NodeJS & PhoneGap 3.3.0 A sidenote: WP8 Projects created with the Cordova Project Templates work perfectly fine. It's the command

问题 I am attempting to build a C++ project in a Visual Studio 2013 solution on TC 8.0.6 (build 27767). I have installed the latest MSBuild "Microsoft Build Tools 2013" stuff (which is normally installed as part of VS 2013 install) directly on the server. But I get the following error: [17:05:23]VCTargetsPath is c:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\ [17:05:23]PlatformToolset is v120 [17:05:23]VCMessage [17:05:23]c:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\Platforms\Win32

问题 I am attempting to build a C++ project in a Visual Studio 2013 solution on TC 8.0.6 (build 27767). I have installed the latest MSBuild "Microsoft Build Tools 2013" stuff (which is normally installed as part of VS 2013 install) directly on the server. But I get the following error: [17:05:23]VCTargetsPath is c:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\ [17:05:23]PlatformToolset is v120 [17:05:23]VCMessage [17:05:23]c:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\Platforms\Win32

问题 Out of curiosity, I've created 2 assemblies which both have a class ( Class1 ) with the exact same namespace ( Library1 ). I then create another client referencing those 2 assemblies and try to create an instance of Class1 . The compiler, not surprisingly, gives me a compile-error about the ambiguous reference. Is there any way to explicitly specify the type in the assembly I want to use to avoid the ambiguity? Note: I know this rarely, if ever at all, happens in practice. It's just a

问题 I have an XNA 3.1 content project (.contentproj) with the following: <ItemGroup> <Compile Include="tiles\B000N800.BMP"> <Name>B000N800</Name> <Importer>TextureImporter</Importer> <Processor>TextureProcessor</Processor> </Compile> <Compile Include="tiles\B000N801.BMP"> <Name>B000N801</Name> <Importer>TextureImporter</Importer> <Processor>TextureProcessor</Processor> </Compile> (... and so on ...) </ItemGroup> What I'd like to do is be able to specify a wildcard so that tiles\*.bmp gets