Hi Ray,
It sounds like your merges are touching the file system in a way (or
location) that affects the application's root. Is it possible to do your
merging in a separate application area?
Here's more on restarts:
http://msdn2.microsoft.com/en-us/library/ms178473.aspx
Ken
Microsoft MVP [ASP.NET]
"Application Restarts
Modifying the source code of your Web application will cause ASP.NET to
recompile source files into assemblies. When you modify the top-level items
in your application, all other assemblies in the application that reference
the top-level assemblies are recompiled as well.
In addition, modifying, adding, or deleting certain types of files within
the application's known folders will cause the application to restart. The
following actions will cause an application restart:
Adding, modifying, or deleting assemblies from the application's Bin folder.
Adding, modifying, or deleting localization resources from the
App_GlobalResources or App_LocalResources folders.
Adding, modifying, or deleting the application's Global.asax file.
Adding, modifying, or deleting source code files in the App_Code directory.
Adding, modifying, or deleting Profile configuration.
Adding, modifying, or deleting Web service references in the
App_WebReferences directory.
Adding, modifying, or deleting the application's Web.config file.
When an application restart is required, ASP.NET will serve all pending
requests from the existing application domain and the old assemblies before
restarting the application domain and loading the new assemblies."
Ray Booysen said:
In our application, we merge documents for our clients. The directory
structure is as follows:
webroot
->bin
->Documents
->Company
-> Company X
-> Company Y
If I create a new folder under Company:
webroot
->bin
->Documents
->Company
-> Company X
-> Company Y
-> New Company
The application immediately restarts. Nothing is in the Event log. What
am I missing?
Kind Regards
Ray Booysen