Whenever you delete a directory under an iis virtual directory it issues an app restart. Just like changing a web.config file or updating a dll. I ran into this a long time ago and found several useful posts and a connect bug which was never resolved. Here is the best one I could quickly find.
http://blogs.msdn.com/toddca/archive/2005/12/01/499144.aspx Adam On Dec 4, 11:01 am, Bergius <[EMAIL PROTECTED]> wrote: > So... After working up some energy by typing this down, I decided to > go on a systematic comment-and-rebuild spree in my > GlobalApplication.cs. Turns out that the deletion of Lucene indexes, > which currently happens on application start (for testing purposes), > seems to have something to do with this... All is well if I don't > delete the index directories. Very odd (right?). Had these directories > resided in application-path\bin, I'd feel a bit more ok with it, but > they're located in application-path\Index. > > Also very odd that my startable components seem to amplify the > problem. > > Still not much wiser, but closer to enlightenment. If you have any > ideas, please share them. > > On Dec 4, 5:13 pm, Bergius <[EMAIL PROTECTED]> wrote: > > > I'm getting some very strange behavior from my app. The symptom is > > simple enough: after rebuilding the app or recycling the app pool, IIS > > starts the app and serves a request successfully, then dies silently > > (or something -- w3wp still lives). New request equals new app start. > > Sometimes the app "sticks" after two or more requests, sometimes it > > just doesn't want to stay alive. > > > I have no idea if this has anything to do with Windsor, MonoRail or my > > own components, but when I remove certain startable components the > > symptom is subtly changed -- fewer or no "restarts" are required to > > make the app stay alive. > > > When debugging w3wp during app start, I see a lot of exceptions, such > > as EEFileLoadException and HRException and groups of up to ~80 > > identical lines saying: > > > "First-chance exception at 0x76d042eb in w3wp.exe: 0xE0434F4D: > > 0xe0434f4d." > > > I don't know if these exceptions are related to my problem. > > > Any ideas how I should go about finding the root of this evil? I'm > > tired of having to massage my app into action :). --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Castle Project Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/castle-project-users?hl=en -~----------~----~----~----~------~----~------~--~---
