G
Guest
I've seen many articles that claim the files in the App_Code directory are
treated in the same way as aspx-files in ASP 1.1. Well, this does not seem to
be the case, at least in Web Developer 2005 Express Beta2. If I change
anything in any of the class files residing in App_Code, the AppDomain is
unloaded and all application data, including all sessions, is lost. Is there
anything I can do to prevent this?
This undesired side-effect means that I still cannot make any changes in a
critical production site without informing the customer in advance and
running the service down at a predefined time. Aspx-files are still the only
files that can be modified at runtime without unloading the AppDomain.
Why can't the new assembly be loaded in the current AppDomain? And is this
going to change for the final release or is the feature by design?
treated in the same way as aspx-files in ASP 1.1. Well, this does not seem to
be the case, at least in Web Developer 2005 Express Beta2. If I change
anything in any of the class files residing in App_Code, the AppDomain is
unloaded and all application data, including all sessions, is lost. Is there
anything I can do to prevent this?
This undesired side-effect means that I still cannot make any changes in a
critical production site without informing the customer in advance and
running the service down at a predefined time. Aspx-files are still the only
files that can be modified at runtime without unloading the AppDomain.
Why can't the new assembly be loaded in the current AppDomain? And is this
going to change for the final release or is the feature by design?