msbuild

Full list of /P MSDeploy arguments for MSBuild from TeamCity

梦想与她 提交于 2019-12-20 17:04:33
问题 I currently use the MSBuild runner in TeamCity for continuous integration on my local server and this works very well. However, I'm having trouble finding a full list of supported command line switches for MSDeploy in the format that TeamCity expects them. In my 'Parameters' section at the moment I using the following switches: /P:Configuration=OnCommit /P:DeployOnBuild=True /P:DeployTarget=MSDeployPublish /P:MsDeployServiceUrl=https://CIServer:8172/MsDeploy.axd /P:AllowUntrustedCertificate

Full list of /P MSDeploy arguments for MSBuild from TeamCity

浪子不回头ぞ 提交于 2019-12-20 17:03:38
问题 I currently use the MSBuild runner in TeamCity for continuous integration on my local server and this works very well. However, I'm having trouble finding a full list of supported command line switches for MSDeploy in the format that TeamCity expects them. In my 'Parameters' section at the moment I using the following switches: /P:Configuration=OnCommit /P:DeployOnBuild=True /P:DeployTarget=MSDeployPublish /P:MsDeployServiceUrl=https://CIServer:8172/MsDeploy.axd /P:AllowUntrustedCertificate

How to fix “No way to resolve conflict between” error?

末鹿安然 提交于 2019-12-20 15:59:13
问题 Recently added log4net.dll to our data object. Our data object builds perfectly but when you try to build anything that references our data object you get the following error: No way to resolve conflict between "log4net, Version=1.2.10.0, Culture=neutral, PublicKeyToken=692fbea5521e1304" and "log4net, Version=1.2.9.0, Culture=neutral, PublicKeyToken=b32731d11ce58905". Choosing "log4net, Version=1.2.10.0, Culture=neutral, PublicKeyToken=692fbea5521e1304" arbitrarily. I found the following

How to fix “No way to resolve conflict between” error?

南笙酒味 提交于 2019-12-20 15:58:09
问题 Recently added log4net.dll to our data object. Our data object builds perfectly but when you try to build anything that references our data object you get the following error: No way to resolve conflict between "log4net, Version=1.2.10.0, Culture=neutral, PublicKeyToken=692fbea5521e1304" and "log4net, Version=1.2.9.0, Culture=neutral, PublicKeyToken=b32731d11ce58905". Choosing "log4net, Version=1.2.10.0, Culture=neutral, PublicKeyToken=692fbea5521e1304" arbitrarily. I found the following

msbuild SLN and still get separate project outputs?

自作多情 提交于 2019-12-20 14:09:02
问题 I have a normal SLN file, and I'm compiling it fine with msbuild from the command line. I do this: C:\slndir> msbuild /p:OutDir=C:\slnbin\ And it dumps everything into C:\slnbin, except for websites, which get deployed to C:\slnbin_PublishedWebsites\. What I would like is to not only have all the binaries dropped in the bin dir, but also have each executeable program have it's own "deployed" folder, similar to what each website gets. So, for example, If I have the following projects: - Common

MSBuild 15.0 (Visual Studio 2017) error MSB4067 for SSDT (SSRS and SSAS) projects: “The element <State> beneath element <Project> is unrecognized”

99封情书 提交于 2019-12-20 12:15:17
问题 MSBuild 14.0 (the version included with Visual Studio 2015) logs warnings (MSB4078) when building a solution which contains SSDT projects (rptproj or dwproj projects). For example: warning MSB4078: The project file "Reports.rptproj" is not supported by MSBuild and cannot be built. This is fine, MSBuild does not support SSDT projects, and we have to fall back to building them with Visual Studio (i.e. devenv.com ). See, for example, this answer. When using MSBuild 15.0 (the version included

How do I restore a property sheet to its default value?

别等时光非礼了梦想. 提交于 2019-12-20 11:56:22
问题 Let's say I carry out the following steps immediately after first installing and opening Microsoft Visual Studio 2010: File -> New -> Project -> Win32 Console App -> Finish . Go to the Property Manager pane -> Expand Debug | Win32 -> Right click Microsoft.Cpp.Win32.user -> Select Properties . Wildly change settings in a clueless manner, and generally act like a fool. Click Apply , save the project, and close Visual Studio. How do I restore the Microsoft.Cpp.Win32.user property sheet to its

How to use MSBuild extension's Zip task?

萝らか妹 提交于 2019-12-20 11:33:11
问题 I decided to use MSBuild Extension's Zip task to compress some of my source code at every build. However, this not works: <UsingTask TaskName="MSBuild.ExtensionPack.Compression.Zip" AssemblyFile="MSBuild.ExtensionPack.dll" /> <Target Name="AfterBuild"> <CallTarget Targets="ZipSourceFiles" /> </Target> <Target Name="ZipSourceFiles" Condition="'$(ConfigTransform)'=='ImRunningOnTheServer'"> <MSBuild.ExtensionPack.Compression.Zip TaskAction="Create" CompressFiles="c:\source.txt" ZipFileName="C:

How to use MSBuild extension's Zip task?

≯℡__Kan透↙ 提交于 2019-12-20 11:32:09
问题 I decided to use MSBuild Extension's Zip task to compress some of my source code at every build. However, this not works: <UsingTask TaskName="MSBuild.ExtensionPack.Compression.Zip" AssemblyFile="MSBuild.ExtensionPack.dll" /> <Target Name="AfterBuild"> <CallTarget Targets="ZipSourceFiles" /> </Target> <Target Name="ZipSourceFiles" Condition="'$(ConfigTransform)'=='ImRunningOnTheServer'"> <MSBuild.ExtensionPack.Compression.Zip TaskAction="Create" CompressFiles="c:\source.txt" ZipFileName="C:

How do I get TeamCity to create the .git directory when cloning a repo for build?

假如想象 提交于 2019-12-20 11:03:51
问题 I'm trying to run a custom command in my MSBuild file; it basically runs 'git log -10' and stores that commit info into a text file. The problem is, when I try to run the build, it errors saying "fatal: Not a git repository". So I checked TeamCity's work directory for my project, and there is no .git directory! Why doesn't TeamCity create the .git directory when it clones the repository? Is there a way to enable this? edit: TeamCity version is 7.1.2; I'll try updating to 8.0.1 to see if there