This documentation is archived and is not being maintained.

How to: Handle Errors in Office Projects

Because of the way that managed code interacts with unmanaged code, Visual Studio does not display errors that are thrown by Microsoft Office 2003 and Microsoft Office 2007 applications. To see these errors, set the debugger to break on common language runtime exceptions.


The dialog boxes and menu commands you see might differ from those described in Help depending on your active settings or edition. To change your settings, choose Import and Export Settings on the Tools menu. For more information, see Visual Studio Settings.

To break on common language runtime exceptions

  1. On the Debug menu, click Exceptions.

  2. Select the check boxes next to Common Language Runtime Exceptions.

All exceptions will now break into the debugger, including ones that you have handled and some first-chance exceptions from the runtime itself, which might not be relevant to your project. Errors referring to msosec not being found appear in every project, but are safe to ignore. These msosec exceptions will not affect your solution.

You can also use Try...Catch statements around your methods to catch exceptions. For more information, see How to: Test Code with a Try…Catch Block in Visual Basic and How to: Handle an exception using Try/Catch (Visual C#).

By default, Visual Studio also does not display Just-In-Time debugging errors for Office projects; however, you can enable this feature so that you can see the errors that are raised. For more information, see Just-In-Time Debugging.

See Also