By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
446,361 Members | 1,683 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 446,361 IT Pros & Developers. It's quick & easy.

Releasing updates to virtual directory

P: n/a
Are there any best practices on releasing updates of an ASP.Net application
to a virtual directory in a production environment? E.g. is it okay to
simply copy over changes to ASP.Net pages in to the virtual directory whilst
IIS is still running or should IIS be stopped first?

--
McGeeky
http://mcgeeky.blogspot.com

Nov 19 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
Hi McGeeky,

Well, first it depends on how your ASP.Net app is structured. Are you using
compiled DLLs or simply text files (.aspx, .asmx, etc)? If using compiled
DLLS, are you using a single DLL, or an app DLL and class library
assemblies? And what exactly are you replacing? Only Page template files,
DLLs, or both?

If you are replacing only text files, you may be able to get away with
replacing the text files while the app is running. However,
interdependencies between pages may cause some logged-in users to experience
exceptions if they are using any pages that are interdependent with other
pages that are changed, or if they are using pages that you replace that are
interdependent with unchanged pages.

If you replace the web.config file, or the dll, the app will restart, and
this may cause problems with logged-in users as well, as it kills all
current Sessions, and re-initializes the application. In fact, you might
just as well expect that in almost any scenario, you may cause problems for
currently logged-in users.

Of course, restarting IIS, or an application pool (in IIS 6) is going to
have the same effect, so in either case logged-in users are going to
experience difficulties.

So, the most important thing to keep in mind is to make changes when there
is as little traffic on the site as possible.

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer
Neither a follower nor a lender be.

"McGeeky" <an**@anon.com> wrote in message
news:uf**************@TK2MSFTNGP10.phx.gbl...
Are there any best practices on releasing updates of an ASP.Net
application to a virtual directory in a production environment? E.g. is it
okay to simply copy over changes to ASP.Net pages in to the virtual
directory whilst IIS is still running or should IIS be stopped first?

--
McGeeky
http://mcgeeky.blogspot.com

Nov 19 '05 #2

P: n/a
That is really useful advice, thanks Kevin!

--
McGeeky
http://mcgeeky.blogspot.com
"Kevin Spencer" <ke***@DIESPAMMERSDIEtakempis.com> wrote in message
news:uE**************@TK2MSFTNGP12.phx.gbl...
Hi McGeeky,

Well, first it depends on how your ASP.Net app is structured. Are you
using compiled DLLs or simply text files (.aspx, .asmx, etc)? If using
compiled DLLS, are you using a single DLL, or an app DLL and class library
assemblies? And what exactly are you replacing? Only Page template files,
DLLs, or both?

If you are replacing only text files, you may be able to get away with
replacing the text files while the app is running. However,
interdependencies between pages may cause some logged-in users to
experience exceptions if they are using any pages that are interdependent
with other pages that are changed, or if they are using pages that you
replace that are interdependent with unchanged pages.

If you replace the web.config file, or the dll, the app will restart, and
this may cause problems with logged-in users as well, as it kills all
current Sessions, and re-initializes the application. In fact, you might
just as well expect that in almost any scenario, you may cause problems
for currently logged-in users.

Of course, restarting IIS, or an application pool (in IIS 6) is going to
have the same effect, so in either case logged-in users are going to
experience difficulties.

So, the most important thing to keep in mind is to make changes when there
is as little traffic on the site as possible.

--
HTH,

Kevin Spencer
Microsoft MVP
.Net Developer
Neither a follower nor a lender be.

"McGeeky" <an**@anon.com> wrote in message
news:uf**************@TK2MSFTNGP10.phx.gbl...
Are there any best practices on releasing updates of an ASP.Net
application to a virtual directory in a production environment? E.g. is
it okay to simply copy over changes to ASP.Net pages in to the virtual
directory whilst IIS is still running or should IIS be stopped first?

--
McGeeky
http://mcgeeky.blogspot.com


Nov 19 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.