msbuild

error MSB4067: The element <When> beneath element <Choose> is unrecognized

99封情书 提交于 2019-12-12 08:27:05
问题 I have the following code: <Import Project="C:\Program%20Files%20(x86)\MSBuild\ExtensionPack\4.0.13.0\x64\MSBuild.ExtensionPack.tasks" /> <PropertyGroup> <Workspace></Workspace> <SolutionName></SolutionName> <TargetEnv></TargetEnv> <DeployPath></DeployPath> <TargetBranch></TargetBranch> <BuildNumber></BuildNumber> <Revision></Revision> </PropertyGroup> <Target Name="assinfo"> <Choose> <When Condition=" '$(TargetEnv)'=='development' "> <PropertyGroup> <Revision>1</Revision> </PropertyGroup> <

SolutionDir set to *Undefined* in post-build xcopy event

假装没事ソ 提交于 2019-12-12 08:26:26
问题 I have a project that has a post-build event that xcopies a DLLs to a certain directory: xcopy "$(TargetDir)$(TargetName).dll" "$(SolutionDir)..\UdpLocationService\bin\Plugins\" /d /y xcopy "$(TargetDir)$(TargetName).pdb" "$(SolutionDir)..\UdpLocationService\bin\Plugins\" /d /y However, I have CruiseControl.NET set up as a build server and MSBuild is failing on building that project due to this xcopy post-build event: MSB3073: The command "xcopy "C:\Build\Services\Windows\VehicleServer

ALINK : warning AL1073: Referenced assembly 'mscorlib.dll' targets a different processor

霸气de小男生 提交于 2019-12-12 08:17:33
问题 We are using VS2013 and .Net 4.5.1(recently migrated, but this error is there from .Net 4.0) . This error occurs only when compiling the project in platform target x64. Is this really a error which will break in runtime? Why MSBUILD does not resolve this mrcorlib.dll properly ? This happens only in projects which were created in VS2010 and does not occur in newly created projects. What am I missing here. All my third party assemblies are in x64bit. In TeamCity build server, I get following

Is a separate Delphi XE4 license required for a build machine?

孤人 提交于 2019-12-12 08:12:39
问题 For building applications via dcc32 onto build server I could use Delphi Trial. There wasn't any problems with licenses for such approach. Now, I am going to use building Delphi XE4 applications onto TeamCity via msbuild . Do I need to have a separate license Delphi XE4 reguired for a build machine? Thank you in advance! 回答1: From the license.rtf file distributed with XE4: 2.4. Command Line Compiler. Licensee may install the command line compiler on a separate computer from the Product itself

Visual Studio 2008 locks dll in bin folder and doesn't let go of it

夙愿已清 提交于 2019-12-12 08:07:04
问题 I am working on a solution consisting of 8 .NET projects. Since I am practicing TDD, I have to re-compile my solution very often. Lately I have been getting the following error about every second time when trying to compile: Error 2 Unable to copy file "obj\Debug\Zeiterfassung.Tests.dll" to "bin\Debug\Zeiterfassung.Tests.dll". The process cannot access the file 'bin\Debug\Zeiterfassung.Tests.dll' because it is being used by another process. Zeiterfassung.Tests.dll is the dll generated by one

Invoke EntityDeploy build task programmatically

可紊 提交于 2019-12-12 07:54:12
问题 I'm using Roslyn to compile, emit and run C# source code. However, I've run into a limitation when faced with projects that use EntityFramework. It seems that simply emitting the compilation isn't enough, as there is an EntityDeploy build task that manipulates the DLLs after they've been emitted. (I believe it is embedding Metadata Artifacts in the DLLs after they're emitted). In the .csproj file I'm processing, I see the following entity deploy task: <EntityDeploy Include="Models\Northwind

How can one modify an ItemDefinitionGroup from an MSBuild target?

孤街醉人 提交于 2019-12-12 07:37:56
问题 I have an msbuild script I wrote to compile Google Protocol Buffers files: <ItemGroup> <ProtocolBuffer Include="Whitelist.proto" /> <ProtocolBuffer Include="Whitelist2.proto" /> </ItemGroup> <ItemDefinitionGroup> <ProtocolBuffer> <ProtoPath>$(ProjectDir)</ProtoPath> </ProtocolBuffer> </ItemDefinitionGroup> <PropertyGroup> <ProtoC>$([System.IO.Path]::GetFullPath($(ProjectDir)..\ThirdParty\protobuf-2.4.1\protoc.exe))</ProtoC> <ProtoOutPath>$(IntDir)CompiledProtocolBuffers</ProtoOutPath> <

Package version is always 1.0.0 with dotnet pack

只谈情不闲聊 提交于 2019-12-12 07:29:23
问题 TLDR: Where is dotnet pack pulling the version information when it creates the nuget package for an assembly? I have a library, that I had transitioned from a .NET 4.6.1 project to a .NET Core project with project.json . For my CI during this period (using TFS 2015 vnext), I would get my version number and replace the version number in the project.json file with the new version. The dotnet pack command would pick the version up just fine, and create a new package with the updated version

How to invoke the same msbuild target twice with different parameters from within msbuild project file itself

泄露秘密 提交于 2019-12-12 07:09:34
问题 I have the following piece of msbuild code: <PropertyGroup> <DirA>C:\DirA\</DirA> <DirB>C:\DirB\</DirB> </PropertyGroup> <Target Name="CopyToDirA" Condition="Exists('$(DirA)') AND '@(FilesToCopy)' != ''" Inputs="@(FilesToCopy)" Outputs="@(FilesToCopy -> '$(DirA)%(Filename)%(Extension)')"> <Copy SourceFiles="@(FilesToCopy)" DestinationFolder="$(DirA)" /> </Target> <Target Name="CopyToDirB" Condition="Exists('$(DirB)') AND '@(FilesToCopy)' != ''" Inputs="@(FilesToCopy)" Outputs="@(FilesToCopy -

Can't find xsd.exe in the path during MSBuild Community Tasks BeforeBuild step in Visual Studio

為{幸葍}努か 提交于 2019-12-12 06:59:27
问题 I am using MSBuild Community Tasks to run Xsd.exe as part of my build in Visual Studio as thus: <Import Project="$(SolutionDir)Common.targets" /> <PropertyGroup> <MSBuildCommunityTasksPath>$(SolutionDir)TeamBuildTypes</MSBuildCommunityTasksPath> </PropertyGroup> <Import Project="$(MSBuildCommunityTasksPath)\MSBuild.Community.Tasks.Targets" /> <UsingTask TaskName="XSD" AssemblyFile="$(VCTargetsPath)$(CPPTasks)" /> <Target Name="BeforeBuild"> <!--Exec Command="'$(DevEnvDir)..\Tools\vsvars32.bat