msbuild

Installshield Build Automation

雨燕双飞 提交于 2019-12-29 08:44:11
问题 I have seen many solutions for automating my InstallShield build, but I am having issues with each one. I am using InstallShield Professional 2013. Sorry for the lengthy question, but I am clueless on which direction to go to solve my issues. 1) IsCmdBld.exe - I have a script that runs and will build my installer. BUT, when the installer runs, I get an error message that says "The System Administrator has set policies to prevent this installation" . I am not sure why this is happening, but I

How can we include the files created by ajaxmin in the msdeploy package created by MSBuild

时间秒杀一切 提交于 2019-12-29 08:40:47
问题 We use ajaxmin to create .min.js files from all our .js files. We have edited the .csproj file of the project and added following: <Import Project="$(MSBuildExtensionsPath32)\Microsoft\MicrosoftAjax\ajaxmin.tasks" /> <Target Name="AfterBuild"> <ItemGroup> <JS Include="**\*.js" Exclude="**\*.min.js" /> </ItemGroup> <AjaxMin JsSourceFiles="@(JS)" JsSourceExtensionPattern="\.js$" JsTargetExtension=".min.js" /> </Target> This works great when we build the site on our workstation and the .min.js

Cruise Control .Net not showing Nant build errors

孤者浪人 提交于 2019-12-29 08:12:34
问题 We are running Cruise Control 1.5.7256.1 and using it to do builds using Nant and Nantcontrib. The builds are failing and succeeding correctly, but when they fail the related error messages are being shown on the CCNet Build Report page. See image below The build errors can be seen on the View Build Log page, but they aren't making it through to the Build Report page. The build itself is pretty simple, it's just a Nantcontrib msbuild element that builds a .Net 3.5 .sln file. Any ideas? 回答1:

Why is Visual Studio 2013 using the wrong SdkToolsPath for lc.exe?

﹥>﹥吖頭↗ 提交于 2019-12-29 07:03:39
问题 I am using Visual Studio 2013 with an asp.net project. One of the projects gives the error below. Why is it looking for LC.exe in the wrong path? My Windows 8.1 SDK is installed and I have an lc.exe at C:\Program Files (x86)\Microsoft SDKs\Windows\v8.1A\bin\NETFX 4.5.1 Tools and a 64bit version and I have a registry key at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SDKs\Windows\v8.1A I am looking at Microsoft.Common.targets under C:\Windows\Microsoft.NET\Framework\v4.0.30319 and this key

TFS2010 Build Definition to Deploy to multiple servers?

南笙酒味 提交于 2019-12-29 05:24:06
问题 I've been looking into TFS2010 new build and deployment features with MSDeploy. So far everything is going well (although its been hard to find information about specific scenarios). Can I modify my Build Definition to specify 2 or more servers to deploy to? What I need to do is deploy to multiple servers (as I have two in my testing environment which uses a NLB). What I have now is a Build definition which Builds, runs my tests, and then Deploys to ONE of my testing servers (which has the

How to query MSBUILD file for list of supported targets?

孤者浪人 提交于 2019-12-29 03:39:10
问题 Is there any way to ask msbuild what build targets provided msbuild file support? If there is no way to do it in command prompt? May be it could be done programmatically? Are there no way to do it besides parsing msbuild XML? 回答1: Updated for .NET Framework 4, since the above has been deprecated. Import microsoft.build.dll and code is as follows: using System; using Microsoft.Build.Evaluation; class MyTargets { static void Main(string[] args) { Project project = new Project(args[0]); foreach

How do you pass conditional compilation symbols (DefineConstants) to msbuild

只谈情不闲聊 提交于 2019-12-28 14:08:05
问题 So, both this and this are pretty clear. Simply pass /p:DefineConstants="SYMBOL" It doesn't work at all for me, even in a test project. I'm expecting that passing /p:DefineConstants="SYMBOL" will override any conditional compilation constants defined in the csproj. Not the case however... Full code listing below: using System; using System.Collections.Generic; using System.Linq; using System.Text; namespace DefineConstants { class Program { static void Main(string[] args) { #if DEV Console

How do you pass conditional compilation symbols (DefineConstants) to msbuild

感情迁移 提交于 2019-12-28 14:08:02
问题 So, both this and this are pretty clear. Simply pass /p:DefineConstants="SYMBOL" It doesn't work at all for me, even in a test project. I'm expecting that passing /p:DefineConstants="SYMBOL" will override any conditional compilation constants defined in the csproj. Not the case however... Full code listing below: using System; using System.Collections.Generic; using System.Linq; using System.Text; namespace DefineConstants { class Program { static void Main(string[] args) { #if DEV Console

Determine if MSBuild CoreCompile will run and call custom target

▼魔方 西西 提交于 2019-12-28 12:43:06
问题 This seems like an obvious thing to want to do but I have pulled most of my hair out trying to find any examples on the web or do it myself. I have a c# solution with 19 projects and a Jenkins build server running a build script to drive MSBuild. MSBuild will of course determine what does and does not need to be compiled based on inputs versus outputs. I am trying to create a custom target to conditionally update the AssemblyInfo.cs of those projects MSBuild is going to compile to increment

What are the MSBuild project level properties for Delphi?

半世苍凉 提交于 2019-12-28 12:05:14
问题 The Delphi documentation for MSBuild says /property:name=value sets or overrides project-level properties, where name is the property name and value is the property value. Use a semicolon or a comma to separate multiple properties, or specify each property separately. /p is also acceptable. For example: /property:WarningLevel=2;OutputDir=bin\Debug I can't find a list of available properties, here's what I know so far: WarningLevel OutputDir (dcc32 -e equivalent) Config I'd like to get a