Last post Dec 04, 2010 03:54 AM by joydeep1985
May 16, 2010 01:45 PM|MyScreenNameWasTaken|LINK
I am trying to publish to a server under my desk, like so:
Build configuration: Debug
Publish method: Web Deploy
Service URL: http://www02
Site/application: sitename <-- obviously this is not actually 'sitename'
Mark as IIS application on destination [ YES ]
Leave extra files on destination [ YES ]
I get the most stupid error considering that I'm publishing this site for the first time. :
Error 1 Web deployment task failed.((16/05/2010 14:22:58) An error occurred when the request was processed on the remote computer.)
(16/05/2010 14:22:58) An error occurred when the request was processed on the remote computer.
Site 'sitename' does not exist. C:\Program Files\MSBuild\Microsoft\VisualStudio\v10.0\Web\Microsoft.Web.Publishing.targets 3588 5 S26.MyProductName.Web.Application
Thanks for any help.
Actually, I've just found something on Connect:
I'll come back and update this thread.
May 16, 2010 06:10 PM|MyScreenNameWasTaken|LINK
The workaround described does not fix the issue.
May 16, 2010 07:14 PM|MyScreenNameWasTaken|LINK
Got it! It's the stupid and confusing new UI for publishing. You basically just enter Default Web Site\something in the Site box. I have always hated IIS. Its the most bewildering upside down and backward product MS have ever made.
To be clear, the Publish dialogue:
Service URL is Microsoft weirdy language for http://server and Site/application is the confuse-the-customer term for, "just type in Default Web Site". Lord knows why this isn't a wizard that connects to your server and reads down
the existing sites and applications and gives options.
Like everything in IIS, it's confusing and full of ambiguous and wrongly used terminology, it's like the messy cupboard in the house that you never get around to clearing up as you bung more rubbish in it and shut the door.
And just for the record, my published site is not the same as that in VS or when browsing to localhost on my dev box as the CSS files and images are not being found. So it doesn't even do a good job of publishing.
Dec 04, 2010 03:54 AM|joydeep1985|LINK
yeah i am also facing the same problem even after registering with aspnet_regiis utility dont know still whts d problem ....
can someone help me please ?