Bringing down an ASP.NET Application for updates

DotNetKicks.com — Tue, 11 Mar 2008 20:11:57 GMT

You've been kicked (a good thing) - Trackback from DotNetKicks.com

re: Bringing down an ASP.NET Application for updates

Phil Lertora — Wed, 12 Mar 2008 06:53:55 GMT

While this is great and very useful, what would be even more useful is to have an In Testing page that you can allow testers into but no one else.

Again - this alone is great.

Interesting Finds: March 12, 2008

Jason Haley — Wed, 12 Mar 2008 17:05:04 GMT

re: Bringing down an ASP.NET Application for updates

Tom — Wed, 12 Mar 2008 18:16:44 GMT

That is a good idea. But would you really want to have a testing "stage" on your production web server? Wouldn't that be more of the things you would do before you publish to the server?

Is there a scenario where this would be needed in that case? Or are you talking about if you only have one server and test and release on the same box?

re: Bringing down an ASP.NET Application for updates

Jenni — Wed, 12 Mar 2008 19:13:09 GMT

I've used a "In Testing" type flag on production boxes to allow us to do a quick shakedown after a deploy to ensure a deploy has gone smoothly without allowing non-test users to access the system, so any rollout issues dont reflect badly on the system to its users.

Bringing down an ASP.NET Application for updates

Mirrored Blogs — Wed, 12 Mar 2008 19:26:16 GMT

ASP.NET Debugging : Bringing down an ASP.NET Application for updates "One of the really useful,