Can We perform IISRESET in Server without affecting application session ?

Question

0.00/5 (No votes)

See more:

I have a Dotnet applcation comprised of several DLL's . So usually some changes will come in these DLLs , to update each change made in DLL to applcation , i perform the IISRESET command , this affects the other users of the my application.Their session gets disconnected. How can i resolve this..issue ..Is there any options to do without affecting other users ? Kindly explain...

Posted 4-Jul-11 1:25am

Sabari MD

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

ragsta · Answer 1 · 2011-07-04T10:17:00

The only chanche you have (and that I Know) to reload a DLL without the reload of the application context is BY DESIGN, performing and managing at runtime the loading and re-loading of the DLL, but it is far away from a basic design pattern.

Be also aware that IISRESET do more than shutdown your application, it shutdown the entire IIS server so all the users of all webapp deployed on the server got their session lost.
IISREST is not necessary to reload the application,
changing a DLL in the the BIN folder will automatically trigger an application restart.

If you are not confident and prefer to be "personally" sure of the restart you can use a simple and dirty trick.
Open the web.config with notepad, change it in a non disruptive mode " for example add or remove a <space>" and save it.This will casuse quite instantly the context reload.

Another way to cause a relaad of the application without shutting down all the server is to deploy it in a dedicated pool and to perform a recycle of that pool.