I am with GG on this, for any site that involves transactions (not just finacial ones), testing on live is really really dangerous - you would have to reverse out, or stub out the endpoints - which kind of makes the testing obsolete
It is a little bit more than that. It's also the page that gets displayed whilst the site is offline for maintenance + signals ASP.NET to shut down the site. So we keep this file on the server and add a "_" prefix whilst the site is running.
The original solution leaves the site running. So when you change the core site's code/DLL(s) there's a moment where the end user will see an ASP.NET error message - not clean like the app_offline Microsoft solution.
Reason for my vote of 5
This seems to be a better option to me as it doesn't requires any changes to website code, just place an extra file if you need to take website offline and remove it when you are done with maintenance.
Last Visit: 31-Dec-99 19:00 Last Update: 20-Jan-22 9:38