Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

3
  • Not wanting to argue. You give good points. But a simple, compelling reason might be; Restarting an application (giving an outage to users) VS. reloading an XML configuration Commented Aug 3, 2016 at 7:13
  • @ross - any half decent setup will have redundant servers, which you rotate out of the pool for the deployment. Users don't even notice. Commented Aug 3, 2016 at 11:37
  • @Ross - I've never administered a large ASP.net site, but my experience working with Java servlets is that even when there's only a single server, I can update the code for my sites without needing to completely restart the web server, so there's just a handful of seconds delay and users just notice the site being a little bit sluggish. Can you not do such live updates with an ASP.net site? Commented Aug 3, 2016 at 16:35