>I take your point. But I think the argument expressed in that thread was that ASP.NET can have no real way of knowing whether changes to the content of folders below the root are meant to modify the behaviour of the site - so it assumes that they will.
>IIRC, somewhere in that link described a DOS command which could be used to suppress the behaviour - but the problem with that, presumably, is that it would also suppress a recompile when you actually wanted one.
>
>Anyway it looks as if you have two seperate problems
>(a) Something it triggering an unexpected recompilation (this thread)
>(b) The subsequent recycling of the app generates a conflict between the existing instance and the one being spooled up as a replacement (other thread)

It is confirmed. The ongoing automatic restart is being caused by the robot. I stopped the robot for an hour and the application was up and running for 1 hour and counting. I never reached over 25-30 minutes before.

Now, I still cannot understand why one robot doesn't affect the Web site automatic restart and the other does. I will need to isolate one by one the task and see which one is the factor.