ASP.NET Website Released - Best Practices

Question

What is the best practice for releasing a new version of my asp.net application?

I am worried about the users who are currently using the application. If I click the new version, will it throw them out? How does IIS handle open sessions?

I’m looking for an easy way to promote new releases without harming users.

Answer 1

I assume you do not have a load balanced environment with multiple web servers?

In this case, the best you could do is probably:

• Look at your logs and work when you have the least traffic.

• , , .master, , . , .

• app_offline.html .

• .

• app_offline.html .

• , .

Answer 2

- :

• (wwwroot/myAppV1 ​​/, wwwroot/myAppV2/ ..)
• , ( , )
• app_offline.htm
• - IIS , , .

IIS, . , .

Answer 3

Qaru Podcast # 63 , Qaru . - , , , , .

Answer 4

-, DLL , , . cookie , .

Answer 5

( -, ). , , , app_offline.htm . app_offline.htm, - .

Answer 6

:

• -, , , DNS-, , , DNS- , , . () , , envrionment asf.

• , , test.example.com, . www.example.com , , test.example.com. - , cookie RESTful, , . , , , , , .