Re: Modifying application folder structure results in application rest

Actually from my experience it does recycle on create/rename sub folder
event in app_data. Not sure about file's events.

George.

"bruce barker" <brucebarker@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:5EB9AD27-CB4E-4D08-A85F-8A80D3E997B9@xxxxxxxxxxxxxxxx
asp.net runs a file monitor and recycles on any change in any folder under
its vdir except app_data. you have a couple options.

1) switch to fat file system that does not support file monitoring

2) place the sub apps under the app_data folder.

3) (most logical) do not have the /content physical file folder under the
root app's file folder, but create the vdir under the root.


-- bruce (sqlwork.com)


"IUnknown" wrote:


Ok, we are all aware of the situation where modifying the folder
structure (adding files, folders, deleting files, etc) will result in
ASP.NET triggering a recompilation/restart of the application.

In a nutshell, I understand how this can be considered desireable by
some, but I am not one of those people.

My situation is that we have a root site (hosted @
http://www.mydomain.com)
in the root application folder '/'.

This is an ASP.NET 2.0 application, running in it's own application
pool. It is sporatically updated (receives about 1 production build
per quarter). This site isn't allowed to be down.... ever... :)

Beneath this site, in '/content/someOtherApplication' is running an
older .NET 1.1 application in a seperate application pool, configured
as an application in IIS......that receives almost daily updates.

So, when a new build to /content/someOtherApplication is pushed, the
root application '/' restarts as well.

Definitely a bad situation, and something I am looking to avoid.

Aside from telling me to put things in non-nested virtual directories
(which is absolutely not an option), what can I do?

In a perfect world, I would like to simply tell ASP.NET to NOT restart
the apps automagically, but I suspect there is some other means to
configure this so that I can retain that 'feature' for appropriate
scenarios.

Thanks in advance.





.

Relevant Pages

  • Re: Page and Images not found on Localhost
    ... I didn't know that even images could be declared as server controls. ... which may not have been declared as a server control. ... I designated the "project" folder as an application in IIS. ... is the root for anything under it. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Virtual Directory, Paths, Local and Deployed Problem
    ... If you are looking to get to the /images folder from the root. ... In production: http://www.site1.com/images/mygif.gif ... make this a virtual folder in IIS. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: This will stump you
    ... > folder, they are not in the web's root. ... Convert the folder to a subweb - ... > Also clear your IE Temp files ...
    (microsoft.public.frontpage.client)
  • Re: Allocating Internal Flash as Root
    ... folder representing theflash. ... is causing theflashto be mounted, not as the root, by like a storage card. ... have set all the registry settings that I could find in the help ... I boot up the system. ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Sometime the JavaScript function becomes undefined
    ... Can't I capture that folder name and store it in a session variable? ... application is the web site root you'll have to use ... and this in the master ... I always get openWindow is undefined. ...
    (microsoft.public.dotnet.framework.aspnet)
Loading