Building deployment package with Visual Studio 2012

Question

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?

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! — OK999, Feb 28 '16 at 23:09

score 4 · Accepted Answer · edited May 23 '17 at 12:23

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.

edited May 23 '17 at 12:23

Community

1
1

answered Aug 24 '12 at 06:13

alexey

8,360
14
70
102

Is this the solution to your problem? – Aug 24 '12 at 09:38

score -1 · Answer 2 · answered Aug 23 '12 at 14:24

-1

I use this manually, should be a matching msbuild parameter

Using the Publish Web Wizard to Create a Deployment Package

answered Aug 23 '12 at 14:24

joe

1

What parameter do you mean? Manual publishing is not a case. It's on a CI server. – alexey Aug 23 '12 at 14:43

Building deployment package with Visual Studio 2012

2 Answers2