Comments on "Locally publishing a VS2010 ASP.NET web application using MSBuild"

Petkov commented on "Locally publishing a VS2010 ASP.NET web application using MSBuild"

Petkov — Wed, 24 Nov 2010 19:30:56 GMT

Thanks! This is exact what I was looking for

Davinci commented on "Locally publishing a VS2010 ASP.NET web application using MSBuild"

Davinci — Wed, 01 Dec 2010 20:14:01 GMT

This is what I am looking for however there has to be some target missing or property I need to set because I get the error

"The Target PipelinePreDeployCopyAllFilesToOneFolder does not exist in project."

You may have manually set the property or target in your MSBuild project file and not know it.

Right now I can't figure out what property(s) and or target(s) are needed to import the use of Microsoft.Web.Publishing.targets file.

I guess I'll go digging into the
Microsoft.WebApplication.targets to find it. EEK!

Davinci commented on "Locally publishing a VS2010 ASP.NET web application using MSBuild"

Davinci — Wed, 01 Dec 2010 20:18:52 GMT

So I decided to try the Package solution and create a zip file. NO DICE as I get the error.

Package does not exist in the project.

Davinci commented on "Locally publishing a VS2010 ASP.NET web application using MSBuild"

Davinci — Wed, 01 Dec 2010 20:38:37 GMT

Figured out my problem My project targets .NET 2.0 and this only works if you use .NET 4.0

Andrew Newcomb commented on "Locally publishing a VS2010 ASP.NET web application using MSBuild"

Andrew Newcomb — Mon, 13 Dec 2010 13:55:46 GMT

Thanks for a useful post, just what I needed.

I had to make one further change to stop the tokenisation of connection strings in the web.config file.
Search for AutoParameterizationWebConfigConnectionStrings in the post at...
http://sedodream.com/2010/11/11/ASPNETWebApplicationPublishPackageTokenizingParameters.aspx

woofy commented on "Locally publishing a VS2010 ASP.NET web application using MSBuild"

woofy — Mon, 22 Aug 2011 15:02:57 GMT

I created a test web app with VS2010 and this method worked perfectly. However, I tried it on our actual application and it fails with a bunch of errors.

To figure out what was wrong, I set up a new test scenario with my initial test web app by creating a new class library project and then referencing this project (not its DLL) by my web app (I also made sure to put some code in my web app that actually referenced code in the class library). When I tried your command line method, it failed with the same errors that I got when I tried this on our production app. I then removed the reference to the class library project and instead referenced its DLL directly. The build worked just fine after that.

How is one supposed to deal with this situation?

Unknown (google) commented on "Locally publishing a VS2010 ASP.NET web application using MSBuild"

Unknown (google) — Tue, 08 Nov 2011 20:45:58 GMT

Hi,

I encountered the following error when used the above publish to filesystem method

MSB3021 unable to copy because a file or directory with the same name already exists.

Any ideas?

superbDeveloper commented on "Locally publishing a VS2010 ASP.NET web application using MSBuild"

superbDeveloper — Tue, 20 Dec 2011 10:55:59 GMT

thanks works well

sproket99 commented on "Locally publishing a VS2010 ASP.NET web application using MSBuild"

sproket99 — Mon, 09 Apr 2012 08:59:49 GMT

Great post. Thank you very much...

Magnus commented on "Locally publishing a VS2010 ASP.NET web application using MSBuild"

Magnus — Tue, 17 Apr 2012 16:53:22 GMT

Been looking for this for a long time for our build server without finding any good solution. Thank you very much!

Krishan Gahlot commented on "Locally publishing a VS2010 ASP.NET web application using MSBuild"

Krishan Gahlot — Wed, 15 Aug 2012 08:57:59 GMT

A complete article with screen shots to deploy asp.et web applications...
csharpdemos.blogspot.in/2012/08/how-to-deploy-aspnet-website-using-iis-7.html

Per commented on "Locally publishing a VS2010 ASP.NET web application using MSBuild"

Per — Mon, 22 Oct 2012 09:25:30 GMT

Thanks for a great article. These features are surely badly documented and I have myself been looking around a lot for this kind of solution.

Stephan commented on "Locally publishing a VS2010 ASP.NET web application using MSBuild"

Stephan — Mon, 06 May 2013 15:07:00 GMT

We are implementing a pluggable architecture at a client.
We have one ASP.NET MVC web core with N plugins created by separate teams (which go into the Areas folder of the core).
Each plugin is a separate ASP.NET MVC project and we should be able to deploy it.
We want the ability for a plugin team to deploy the plugin by creating a package.
The core should not be redeployed each time.
How would this have to be achieved (custom targets file)?

All content (views, scripts, css) must go into the Areas sub folder of the core.
The dll files must go into the bin folder of the core.

The goal is that an administrative person runs the package (eventually with some customizations).