The behavior you are seeing is somewhat skewed by the debugger. Its altered
to mimic the real world behavior as much as possible. An application is
recycled when, among other things, files are touched in the directory.
Closing visual studio does not touch the files so the application state
remains. However if you save before closing that will trigger a restart of
the app. This closely mimics real world behavior which cause an app to
restart if the config files are dirty, the number of uploaded files exceed
15, the assembly files change, idle time out etc etc.
Makes sense?
--
Regards,
Alvin Bruney [ASP.NET MVP]
Got tidbits? Get it here...
http://tinyurl.com/3he3b
"Bruce W.1" <no@direct.email> wrote in message
news:40**************@direct.email...
I'm storing some things in the application state, like this:
Application["MyValue"] = "whatever";
In Visual Studio, when I shut down the web app then start it again the
application state information remains. If there are no browsers using
the app one would think that this would remove any application state,
but it does not.
However if I wait awhile then the application state information goes
away.
What controls the length of its life?
Thanks for your help.