Question

I want to package my VS2010 web application project ready for deployment with msdeploy. On development machine I can do this using:

MSBuild.exe "C:path	oWebApp.csproj" /target:package

But on my build server I get this error:

error MSB4057: The target "package" does not exist in the project.

What am I missing on the build server?

Answer 1

I just got this working without installing VS2010 by following these steps on the build server:

If .NET Framework 4 isn t installed, install it
Install the Web Deployment tool from http://www.iis.net/download/webdeploy
From the C:Program FilesMSBuildMicrosoftVisualStudiov10.0 folder on your dev machine copy the "Web" and "Web Applications" folders to the equivalent directory on your build server.

This seems to work for me

Answer 2

I know it s an old question, but I recently ran into the same issue and none of the answers helped. I was missing following file on my build server:

C:Program Files (x86)MSBuildMicrosoftVisualStudio
    v11.0WebMicrosoft.Web.Publishing.targets

It is imported by:

C:Program Files (x86)MSBuildMicrosoftVisualStudio
    v11.0WebApplicationsMicrosoft.WebApplication.targets

Hope this helps someone like me :)

Answer 3

You may install MSBuild.Microsoft.VisualStudio.Web.targets package. No need to manually copy targets to build server.

Answer 4

I experienced the same issue. Ended up resolving by adding this:

<PropertyGroup>
<VisualStudioVersion Condition=" $(VisualStudioVersion)  ==   ">10.0</VisualStudioVersion>
<VSToolsPath Condition=" $(VSToolsPath)  ==   ">$(MSBuildExtensionsPath32)MicrosoftVisualStudiov$(VisualStudioVersion)</VSToolsPath>
</PropertyGroup>

<Import Project="$(MSBuildToolsPath)Microsoft.CSharp.targets" />

<Import Project="$(VSToolsPath)WebApplicationsMicrosoft.WebApplication.targets" Condition=" $(VSToolsPath)  !=   " />

<Import Project="$(MSBuildExtensionsPath32)MicrosoftVisualStudiov10.0WebApplicationsMicrosoft.WebApplication.targets" Condition="false" />

to my .csproj fiie.

Answer 5

You need to have .Net 4.0 installed on the build server. The .Net 4.0 install will put the new MSBuild 4.0 which supports packaging web application projects.

Also, when you are running msbuild.exe make sure you are running the one that sits in the .Net 4.0 framework folder.

Answer 6

Also consider using msbuild with version, corresponding to Web Deployment tool version. I have faced same problem as the OP. The solution was to change msbuild from 4.5 to 4.0 on buildServer.

友情链接