9

We were building a Visual Studio 2010 solution with the following msbuild command:

msbuild MySolution.sln /p:DeployOnBuild=true;DeployTarget=Package

This command built the solution and created the deployment packages for web projects in the solution.

But after we've migrated to Visual Studio 2012 this command doesn't work anymore. The solution is built, but no deployment packages are created.

How to fix it?

Improve this question
1
  • can you let me know - if a solution contains non web projects as well, will those be a part of the package that is generated by the msbuild? I am new to the .NET world, and i trying to get the concept of "build once and deploy anywhere". If the non web projects are left out than, my theory to build a single package for the solution is not going to work! Commented Feb 28, 2016 at 23:09

2 Answers 2

Reset to default
4

The problem was exactly the same as in this question. Copying *C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v11.0\Web** from a local machine to a remote CI server.

Improve this answer
Sign up to request clarification or add additional context in comments.

1 Comment

Is this the solution to your problem?
-1

I use this manually, should be a matching msbuild parameter

Using the Publish Web Wizard to Create a Deployment Package

Improve this answer

1 Comment

What parameter do you mean? Manual publishing is not a case. It's on a CI server.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.