Home Dashboard Directory Help

VS2010 sp1 web deployment fails when project url has a trailing slash / by Saffy


 as Fixed Help for as Fixed

Sign in
to vote
Type: Bug
ID: 665405
Opened: 4/28/2011 2:40:13 AM
Access Restriction: Public
User(s) can reproduce this bug


I receive the following error message:

Web deployment task failed.(Object of type 'manifest' and path 'C:\Development\Deployment\NewMatterOpeningForm3e\Archive.SourceManifest.xml' cannot be created.)

Object of type 'manifest' and path 'C:\Development\Deployment\NewMatterOpeningForm3e\Archive.SourceManifest.xml' cannot be created.
One or more entries in the manifest 'sitemanifest' are not valid.
Application '/NewMatterOpeningForm/' does not exist in site 'Nabarro.Finance.NewMatterOpeningForm-Site'.

When using the new web deployment technology to target a server running IIS 7.

I have traced the problem to the project settings. In the Web section, if the Project URL (to the left of the Create Virtual Directory button) has a trailing slash, e.g.
then the above error is caused.

Sign in to post a comment.
Posted by Microsoft on 10/12/2011 at 9:46 AM
Hi Saffy, I have investigated this problem. I wanted to let you know that we have fixed this and you should see the fix in the next version of Visual Studio. I will close this issue, but if you feel that I have misunderstood anything please reactivate it.

Sayed Ibrahim Hashimi | http://sedodream.com
Posted by Theo Harper on 10/7/2011 at 8:49 AM
Has there been any movement on this issue, as I have just wasted a day trying to get publish to work only to be fixed by removing the trailing slash.
Posted by Microsoft on 4/28/2011 at 8:03 PM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.

Posted by Microsoft on 4/28/2011 at 3:13 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)
Sign in to post a workaround.