FYI..

 While trying to overcome the lack of productivity with the vs 2005 VB.NET lockup problems, we duplicated the developer machines, i.e while one was rebooting, the solution could be re-checked out and work could continue...

Anyway, it turns out that in anumber of cases the lockups are not crash related (even though they freeze the machine), but are actually very-very-very slow compiles..

Yes, after about 30 to 40 minutes the compiler actually completes!!! and the machine lockup is removed and the compile is complete..

Dont that just beat all, a 30 to 40 minute compile...

Yes,

 it changes some of the problems, i.e instead of looping with the "send to Msoft" screen, it now shows this once (great) and then crashes vs (not great).. Thried the send problem after reboot, but got sick of this after 20minutes as well..

But realy no progress on fixing the underlying VB.NET cronic problems ( which seem to be memory exception errors , at least thats what happens after the above)..in some threading process) note machines have 2Gis of memory!

With regard to the 30-40 minute compiles will see, we normally dont have this time to waste, but will let you know if it improves..

Also dont see why on sevrer 2003 vs 2005 can lockup all processes while compiling!!

Thanks...

After some more experience with this patch..

It would seem it fixes nothing.. other than removing the internal error traps which used to drive the "report to Msoft" screns then crash..

Now the report to Msoft sceens no longer lockup, and the let the error bubble up to the user, so you see what is typcially an illegal memory access error ( and the assocaited internal VB.NET error code)..

In fact due to the above we get more not less re-starts, but less reboots..

Is this truely the fix?

The compiler is still BROKEN...