Re: Modifying application folder structure results in application rest

re:
!> Actually from my experience it does recycle on create/rename sub folder event in app_data.

Filesystemwatcher events are supposed to be ignored by the ASP.NET runtime.

App_Data is designed not to respond to this filesystemwatcher behavior.

Since directories are a special type of file, anyway, directory changes under App_Data
aren't supposed to trigger filesystemwatcher behavior...but you're right, they do.

"ASP.NET developers know that if you create a new file , modify any file in the application
root or the /bin folder, or modify web.config, this will trigger an application restart."

As a result of extensive testing, using Web Application Projects,
I've found that these are the file events which trigger application restarts :

1. Adding, modifying, or deleting any source code file in any application folder ( *.cs, *.vb, etc. )

2. Adding, modifying or deleting global.asax or web.config.

3. Adding, modifying or creating any assemblies in the /bin folder

4. Adding, modifying, or deleting localization resources
from the App_GlobalResources or App_LocalResources folders.

5. Adding, modifying, or deleting source code files in the App_Code directory.

6. Adding, modifying, or deleting Profile configuration.

7. Adding, modifying, or deleting Web service references in the App_WebReferences directory.

8 Adding, renaming or deleting any directory.

*** If anybody knows of any other event which triggers an application restart,
if a WAP is used, please post the info so the list can be updated. ***

Regarding "standard" web site projects, I need to do more testing,
but I suspect that application restarts won't occur when a single
source file is modified, unless it's located in App_Code.

That would leave items 2-8 in the above list, eliminating only item 1.

*** If anybody has tested the website project scenario and found
different behavior, please post the info so the list can be updated. ***




Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
======================================
"George Ter-Saakov" <gt-nsp@xxxxxxxxxxx> wrote in message news:O1wNshZxIHA.4376@xxxxxxxxxxxxxxxxxxxxxxx
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: Modifying application folder structure results in application rest
    ... After 15th, application will restart. ... Actually from my experience it does recycle on create/rename sub folder ... aren't supposed to trigger filesystemwatcher behavior...but you're right, ... modifying or deleting global.asax or web.config. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Modifying application folder structure results in application rest
    ... the application will restart. ... Actually from my experience it does recycle on create/rename sub folder event in app_data. ... aren't supposed to trigger filesystemwatcher behavior...but you're right, ... modifying or deleting global.asax or web.config. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Field chooser Outlook 2003
    ... My guess is that you're modifying the currently displayed view, ... Sue Mosher, Outlook MVP ... > click in the folder and select field chooser. ... >>>>> over a public folder creates fields to show document properties, ...
    (microsoft.public.exchange.clients)
  • Re: Shell Customization doesnt work like help says
    ... I'd already done this (cloning and modifying the shell for various ... What I did was put this stuff in my platform folder (in the BSP, ... I end up generating the new EXE in a subfolder ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Default View Includes Preview Pane On
    ... Have you tried modifying the default view for messages? ... (From memory... ... > create a new folder, the View setting has the preview pane ON. ...
    (microsoft.public.outlook)
Loading