Visual Studio generates invalid MsDeploy commands when UseMsdeployExe is set

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

Closed

as Fixed

Type:	Bug
ID:	654844
Opened:	3/30/2011 11:00:24 AM
Access Restriction:	Public

Workaround(s)

view

User(s) can reproduce this bug

Setting UseMsdeployExe property in the targets file, as described here: http://blogs.msdn.com/b/webdevtools/archive/2010/11/03/web-deploy-how-to-see-the-command-executed-in-visual-studio-during-publish.aspx results in Visual Studio generating invalid parameters for calling MsDeploy, when you have web.config transformations taking place.

Details (expand)

Visual Studio 2010 SP1

Create a web project, and configure a web.config transformation that changes a connection string parameter. Create a .targets file as described in the blog post here: http://blogs.msdn.com/b/webdevtools/archive/2010/11/03/web-deploy-how-to-see-the-command-executed-in-visual-studio-during-publish.aspx

Then attempt to deploy using the configuration mentioned above. (You should not need to actually create a valid server to deploy to, as it fails before that)

English

Windows 7

English

(Actual path names have been modified)

Start Web Deploy Publish the Application/package to https://staging.server:8172/MsDeploy.axd?site=staging.website ...

C:\Program Files (x86)\IIS\Microsoft Web Deploy V2\msdeploy.exe -source:manifest='\\src\TechEye.Web.UI\obj\Deploy-Staging\Package\TechEye.Web.UI.SourceManifest.xml' -dest:auto,ComputerName='https://staging.server:8172/MsDeploy.axd?site=staging.website',UserName='staging-deploy',Password='XYZ',IncludeAcls='False',AuthType='Basic' -verb:sync -enableRule:DoNotDeleteRule -disableLink:AppPoolExtension -disableLink:ContentExtension -disableLink:CertificateExtension -setParam:kind='ProviderPath',scope='contentPath',match='^src\\Project\.Web\.UI\\obj\\Deploy-Staging\\Package\\PackageTmp$',value=staging.techeye.net -setParam:kind='ProviderPath',scope='setAcl',match='^src\\Project\.Web\.UI\\obj\\Deploy-Staging\\Package\\PackageTmp$',value=staging.techeye.net -setParam:kind='ProviderPath',scope='setAcl',match='^src\\Project\.Web\.UI\\obj\\Deploy-Staging\\Package\\PackageTmp\\App_Data$',value=staging.techeye.net/App_Data -setParam:kind='XmlFile',scope='src\\Project\.Web\.UI\\obj\\Deploy-Staging\\Package\\PackageTmp\\Web\.config$',match="/configuration/connectionStrings/add[@name='N2CMS']/@connectionString",value=server=database.server;database=livedb;user id=livedbuser;password=XYZ -allowUntrusted -retryAttempts=2

MSDEPLOY(0,0): Error : Unrecognized argument 'id=livedbuser;password=XYZ'. All arguments must begin with "-".
MSDEPLOY(0,0): Error count: 1.

Visual Studio should be able to call MsDeploy correctly (and therefore give us some working arguments to call if we want to replicate it's behaviour from a build server).

It appears it is not correctly escaping commands to replace connectionString parameters (because of the space in the "user id"). It's also not very clear why it's having to set these properties manually in the first place.

0 attachments

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.

Thanks,
- Jimmy Lewis
SDET, Visual Web Developer team

Posted by Robb Schiefer 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(http://support.microsoft.com)