Jack is Here, asp.net findings

Symptoms
Consider the following scenario:You use the Dr. Watson program or a third-party debugger to catch unhandled exceptions that may occur when a program is running.You install one of the following Microsoft products:SQL Server 2005 Standard EditionSQL Server 2005 Developer EditionSQL Server 2005 Enterprise EditionSQL Server 2005 Workgroup EditionAny product that contains one of the previously listed products
(For example, you install Microsoft Windows Small Business Server 2003 R2 Premium Edition.)In this scenario, later unhandled exceptions are caught by the Microsoft Visual Studio just-in-time (JIT) debugger. For example, if a Data Execution Prevention (DEP) exception occurs, a dialog box appears that requires user intervention to either start JIT debugging or ignore the exception.
Resolution
This issue occurs because the SQL Server 2005 installation process calls the Visual Studio installation process. The Visual Studio installation process changes the default application debugger to the Visual Studio JIT debugger. This change occurs regardless of which debugger you previously used. You do not receive any notification that this change has occurred.

Symptoms
Visual Basic uses exception code 0xC000008F as its internal exception code. You can ignore the returned float value that the exception returns. Visual Basic is actually making a call to an object that returns a failure HRESULT. That failure is turned into an exception that gets thrown. There is no bug in Visual Basic. Instead, you need to examine the object being called, which causes the exception, and determine why it is failing.
Resolution
This exception may appear in a debug dump generated by the Console Debugger (CDB) or in the WinDbg debugger when you use the Exception Monitor. Please review the CDB or WinDbg debugger sxe switch that allows you to control the action the debugger takes when an exception occurs.For example, you can use the sxe switch to dump the call stack associated with the exception.