Thank you for your quick reply, I'm glad to see you're working hard to develop an even better webserver.
For the second problem:
Quote:Maybe the Interconsult.Engine assembly in not in the Bin folder? Could you please verify that?
Yes, the code in that namespace is in the App_Code folder and gets compiled at the first page request. Even though this was not the problem, thanks to your suggestion I was able to pinpoint the cause, which was in MY code after all ;) Under some circustances, some code I put into Application_Start in global.asax would throw an exception. It's basically a timer which checks jobs to do every a few minutes.
As Microsoft explains here:
http://support.microsoft.com/?scid=kb%3Ben-us%3B911816&x=9&y=14Quote:
Unhandled exceptions outside the context of a request, such as exceptions on a timer thread or in a callback function, cause the worker process to end.
The faulty code, being executed at Application_Start, is indeed out of context and that's why asp.net stopped. Silly me, I should have realized this earlier, even IIS 5.1 stops working when that happens. In that case IIS shows an "Application not available" page, I wonder if Cassini could keep running even on such events, so you're not forced to restart the service.
Also, I was misled into thinking the problem was with Cassini by the fact that on the production server the app is working ok, but just because I found later that legacyUnhandledExceptionPolicy was set to True in the Aspnet.config file.
Until I'll fix the problem, I've set legacyUnhandledExceptionPolicy=True also on my local computer. IIS is now ignoring the unhandled exception, but Cassini is not :/ It still crashes after a few minutes, whenever the faulty code goes to execution.
Many thanks for your support :)
