web-deployment-project

I am trying to build a web deployment project 2010 project for a solution. I have installed the Windows SDK and Web Deployment Project 2010 RTW on the build server, as well as copied over the missing .target files for MSBuild. When attempting to build the project it spits out the following error C:\Program Files\MSBuild\Microsoft\WebDeployment\v10.0\Microsoft.WebDeployment.targets(1589, 9): error MSB6004: The specified task executable location "C:\Program Files\MSBuild\Microsoft\WebDeployment\v10.0\aspnet_merge.exe" is invalid. Unfortunately, searching around Google for results about this

Has anyone got a Web Deployment Project to work with ASP.NET MVC? When I open the "deployed" project, a lot of the files are missing that MVC requires and makes it tough to Publish to the server with all the missing files in the project. Or... Is there a better way than a Web Deployment Project to modify the Web.Config for MVC apps? I have differences (SMTP and connection strings) that need to be updated before uploading and Web Deployment Projects seem to be the right method. Thanks as always! Update: I am missing at least global.asax, global.asax.cs, and default.aspx.cs. Update 2: Once I

For VS2010 and before I was utilizing Web Deployment Projects (WDP) to help package my website for production deployment. I had a MSBuild script that compiled the solution in release mode. An output of that was production ready website files compiled and cleaned by the WDP. I see for 2012 WDP have been removed, and a new tab has been created in the properties for the web application. The options are the same, but now the invocation of this is done via the Publish option (before you just compiled in release mode). So the question is this. From an MSBuild script, how do I invoke a Publish

I currently use Web Deploy, http://learn.iis.net/page.aspx/346/web-deploy/ to publish my MVC2 app. It used to work well, but now it is got to the point where I can't continue using it: When the MVC app was small and had only a few users it was easy to publish. Just right click the project in Visual Studio and choose "Publish". And because there were only a few users it was easy to find a time when no one was using the site to do a quick update. Then the app got bigger and had a few more users. The "Publish" action started taking longer and longer and occasionally timing out. Even when I

I had v1 of msdeploy installed and I uninstalled it to install the v2. Now my vs2010 packages fail when I run the deploy.cmd because it can't find the registry entry - even though I've created an MSDeployPath environment variable pointing to the v2 path? I have MSDeployPath set to "C:\Program Files\IIS\Microsoft Web Deploy V2" in the Advanced System Settings/Environment Variables under My Computer/Properties. The error I get when I run the VS2010 deploy.cmd file is: Files\IIS\Microsoft was unexpected at this time. Anyone know how to fix this? The vs2010 package's deploy.cmd looks for /1 in the