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. 5  2606 
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.
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" <br*********@discussions.microsoft.comwrote in message
news:5E**********************************@microsof t.com...
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.
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****@cardone.comwrote in message news:O1**************@TK2MSFTNGP06.phx.gbl...
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" <br*********@discussions.microsoft.comwrote in message
news:5E**********************************@microsof t.com...
>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.
Wow, that is extensive testing...Want to add to this list
9. You can make 15 (by default, configurable) changes to .aspx files with
out triggering restart. After 15th, application will restart. Does not
matter what changes to HTML or to code that is in <script runat=server>
George.
"Juan T. Llibre" <no***********@nowhere.comwrote in message
news:%2***************@TK2MSFTNGP05.phx.gbl...
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****@cardone.comwrote in message
news:O1**************@TK2MSFTNGP06.phx.gbl...
>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" <br*********@discussions.microsoft.comwrote in message
news:5E**********************************@microso ft.com...
>>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.
re:
!Wow, that is extensive testing...
<chuckle>
I've sweated meatballs doing that.. <g>
re:
!Want to add to this list
!9. You can make 15 (by default, configurable) changes to .aspx files without
!triggering restart. After the 15th configurable change, the application will restart.
!It doesn't matter whether the changes are to HTML or to code that is in <script runat=server>
Thanks! Added to the list.
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****@cardone.comwrote in message news:O4**************@TK2MSFTNGP03.phx.gbl...
Wow, that is extensive testing...Want to add to this list
9. You can make 15 (by default, configurable) changes to .aspx files with out triggering restart. After 15th,
application will restart. Does not matter what changes to HTML or to code that is in <script runat=server>
George.
"Juan T. Llibre" <no***********@nowhere.comwrote in message news:%2***************@TK2MSFTNGP05.phx.gbl...
>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****@cardone.comwrote in message news:O1**************@TK2MSFTNGP06.phx.gbl...
>>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" <br*********@discussions.microsoft.comwrote in message
news:5E**********************************@micros oft.com...
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.
>
>
>
This thread has been closed and replies have been disabled. Please start a new discussion. Similar topics
by: MisterG |
last post by:
Hi,
In my code, I rename a folder and then the asp.net application restarts !
So i've lost my session variables ...
How is it possible for the application asp.net to restart when you rename a...
|
by: Chris Langston |
last post by:
I have a Web Server running IIS 5 or 6 on Windows 2K and Windows 2003 Server
that is experiencing strange shutdown problems. We are using ASP.NET v1.1
and our application is written in VB.NET
...
|
by: Chris |
last post by:
I'm trying to get an existing VS.NET project up on my Win2003 server and I
get the following error (on the actual website page):
"It is an error to use a section registered as...
|
by: Pint |
last post by:
I would like to know if there is a programatic way to force the
Application object to restart. I have a hosted website where I will be
unable to control the webserver (eg:iisreset), and I would...
|
by: amolkasbekar |
last post by:
Hi All,
I have a asp.net application that I am migrating from 1.1 to 2.0.
The App runs fine in 1.1. My setup is Winxp with IIS5. However, when I
run the app in 2.0, IIS is doing an 'Application...
|
by: Ray Booysen |
last post by:
In our application, we merge documents for our clients. The directory
structure is as follows:
webroot
->bin
->Documents
->Company
-> Company X
|
by: markric |
last post by:
Good day,
I have an ASP.NET application / website with the following type of
structure:
+ wwwroot
+ company site
+ masterpages
+ product1
+ product2
|
by: Brian Simmons |
last post by:
Hi All,
I know that if you modify the web.config file or any file in the App_Code
subfolder, that ASP.net 2.0 will "restart" the application (i.e. clear out
any sessions, etc...).
Are there...
|
by: Sriram Srivatsan |
last post by:
Hi
We are trying to build an application where we render some of the .aspx
pages from the database using a class derived from
System.Web.Hosting.VirtualPathProvider. Users configure the...
|
by: Charles Arthur |
last post by:
How do i turn on java script on a villaon, callus and itel keypad mobile phone
|
by: ryjfgjl |
last post by:
In our work, we often receive Excel tables with data in the same format. If we want to analyze these data, it can be difficult to analyze them because the data is spread across multiple Excel files...
|
by: emmanuelkatto |
last post by:
Hi All, I am Emmanuel katto from Uganda. I want to ask what challenges you've faced while migrating a website to cloud.
Please let me know.
Thanks!
Emmanuel
|
by: BarryA |
last post by:
What are the essential steps and strategies outlined in the Data Structures and Algorithms (DSA) roadmap for aspiring data scientists? How can individuals effectively utilize this roadmap to progress...
|
by: Hystou |
last post by:
There are some requirements for setting up RAID:
1. The motherboard and BIOS support RAID configuration.
2. The motherboard has 2 or more available SATA protocol SSD/HDD slots (including MSATA, M.2...
|
by: marktang |
last post by:
ONU (Optical Network Unit) is one of the key components for providing high-speed Internet services. Its primary function is to act as an endpoint device located at the user's premises. However,...
|
by: Hystou |
last post by:
Most computers default to English, but sometimes we require a different language, especially when relocating. Forgot to request a specific language before your computer shipped? No problem! You can...
|
by: Oralloy |
last post by:
Hello folks,
I am unable to find appropriate documentation on the type promotion of bit-fields when using the generalised comparison operator "<=>".
The problem is that using the GNU compilers,...
|
by: agi2029 |
last post by:
Let's talk about the concept of autonomous AI software engineers and no-code agents. These AIs are designed to manage the entire lifecycle of a software development project—planning, coding, testing,...
| |
