Hi,
Although I didnt actually stop the site, I will try this next time I try to upload.
It took me 4.5 hours today and 9 attempts, so I dont want to try again unless I need to.
More facts:
- I published yesterday without any problems and I didnt stop it then.
- There is nobody using the site yet.
- Also, the App_Offline.htm already gets created by VS when I publish.
- During my 9 attempts today I was manually deleting ALL the files by FTP before publishing.
Main Topics
Browse All Topics





by: abelPosted on 2009-05-21 at 06:33:58ID: 24441172
The problem that might be the cause of you is that the website is not stopped before the update takes place. Normally, I believe that the Publish button is used, that should be taken care off, but apparently it isn't, which is why some files are in use and the full update of the site does not work well.
Personally, for live websites (production servers) I have abandoned the publish button, because of two reasons: it takes too long, sometimes more then 20-fold the FTP time, and it makes mistakes when the website cannot be stopped.
I understand that you would want to use the feature of Visual Studio. My recommendation is to use the App_Offline.htm file (place it in the root of your website and your website goes immediately offline). You can copy it there using a pre-build step when publishing, or, safer, using normal FTP (you can put the command in a batch file for easy use).
To check whether this story holds for your situation, place the App_Offline.htm with a nice message inside the root directory and try publishing again. After publishing, don't forget to remove the App_Offline.htm again.
-- Abel --