Visual Studio generates invalid MsDeploy commands when UseMsdeployExe is set - by James Crowley

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 654844 Comments
Status Closed Workarounds
Type Bug Repros 1
Opened 3/30/2011 11:00:24 AM
Access Restriction Public


Setting UseMsdeployExe property in the targets file, as described here: results in Visual Studio generating invalid parameters for calling MsDeploy, when you have web.config transformations taking place.
Sign in to post a comment.
Posted by Microsoft on 1/27/2012 at 11:31 AM
This should be fixed in the Visual Studio 11 release. I believe this includes the Developer Preview released at BUILD.

- Jimmy Lewis
SDET, Visual Web Developer team
Posted by Robb Schiefer - chief7 on 1/27/2012 at 11:24 AM
I noticed this issue is marked as fixed. What version of VS will have the fix?

I'm using VS2010 SP1 and am having this issue.
Posted by Microsoft on 5/2/2011 at 2:46 PM
Thank you for reporting this issue. It will be fixed in a future release of Visual Studio.
Posted by Microsoft on 3/31/2011 at 2:58 AM
Thank you for submitting feedback on Visual Studio 2010 and .NET Framework. Your issue has been routed to the appropriate VS development team for review. We will contact you if we require any additional information.
Posted by Microsoft on 3/30/2011 at 11:14 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(