Exception at Windows Apps running on 1.0 and 1.1 frameworks side-by-side

[LD]

Hi, everyone! Couple of user's Win 2000 Pro machines historically have
framework 1.0 installed and Windows app (designed in-house), which
successfully runs on it. I have developed app further in VS 2003, and
XCopied new version on those machines for users to test. (Had to
install framework 1.1 for them first, side by side with 1.0.) For 4
straight days everything worked great.

Here is the most interesting part. Today both machines at the same
time are having similar errors in both old and new apps, when you try
to perform only _certain_ operations in the app. Then they exit with
code 0, try to call JIT debugger, do not find it, and freeze entire
app. The rest of the programs run fine though. Few hours later without
any efforts problem goes away. Now we are waiting for the next turn...

Machines are user's ones, no developer's tools installed. I checked
registry HKLM\software\ms\windows nt\current version\AeDebug, and its
very different from mine, developer's one.

Auto 1
Debugger arwtsn32 -p%ld -e%ld -g
UserDebuggerHotKey 0x00000000(0)

Your help is appreciated greatly!

 

[David Browne]

Hi, everyone! Couple of user's Win 2000 Pro machines historically have
framework 1.0 installed and Windows app (designed in-house), which
successfully runs on it. I have developed app further in VS 2003, and
XCopied new version on those machines for users to test. (Had to
install framework 1.1 for them first, side by side with 1.0.) For 4
straight days everything worked great.

Here is the most interesting part. Today both machines at the same
time are having similar errors in both old and new apps, when you try
to perform only _certain_ operations in the app. Then they exit with
code 0, try to call JIT debugger, do not find it, and freeze entire
app. The rest of the programs run fine though. Few hours later without
any efforts problem goes away. Now we are waiting for the next turn...

Machines are user's ones, no developer's tools installed. I checked
registry HKLM\software\ms\windows nt\current version\AeDebug, and its
very different from mine, developer's one.

Auto 1
Debugger arwtsn32 -p%ld -e%ld -g
UserDebuggerHotKey 0x00000000(0)

But you still don't know what the exeption was!

You never want to let the exception get to the debugger. Catch it before it
propagates or at least trap the AppDomain.UnhandledException event and log
the result. Then start to figure out what went wrong and how to fix it.

David