>So add some logging code. Seems to me that at this point you really need to narrow down the problem by getting some hard information on what is actually happening and when. There are too many possibles to just guess......

I have added some log and succeeded to simulate that on my local PC. Basically, I can simulate that at about 80%. What I do is to force a recompile. Then, on the Web site, I click on four options pretty fast so they are all in pending because the site is updating the new DLL. Usually, when clicking pretty fast, at the same time a new DLL is effective, will generate the problem on my PC as well at 80%. So, I am relying on that for my tests.

Basically, an ASPX is having that line at the top:

Page Language="VB" AutoEventWireup="false" Inherits="LevelExtreme.WebForm"

LevelExtreme.WebForm is the DLL and the main class. This class is in LevelExtreme.DLL. It is a sub class of Framework.DLL which contains WebForm.vb.

Framework.WebForm() contains this at the top:

Namespace Framework

    Public Class WebForm
        Inherits System.Web.UI.Page

        Public cMessage As String = ""
        Public oProcess As Framework.LXProcess = New Framework.LXProcess()

        Sub Page_Init(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Init
            App.oApp.CreateFile("1", "d:\iis\level extreme\temp\1.txt")

As you can see, it is inheriting from System.Web.UI.Page. So, at first, Page_Init() is executed. As you can see, the first thing it does is to create a .txt file. I use that for the log. Once my tests will be over, I will remove that. Guess what, when the situation happens, it doesn't even go there.

So, it is either something is done wrong in my design or I have the same configuration problem on my PC and the server.