ansaurus

Question

A bunch of logged exceptions in Microsoft.VisualBasic.dll

Answer 1

+2 A:

It's not limited to converted projects. Some info here :

http://blogs.msdn.com/davidklinems/archive/2005/07/12/438061.aspx

http://www.helixoft.com/blog/archives/24

CodeByMoonlight 2009-09-02 12:22:32

Great! So First time exception is just that an exception is raised somewhere, and if it does not cause a debug stop somewhere, it just means that the exception was handled properly...

awe 2009-09-02 13:14:20

... and the first link tells us how to not display them in the Immediate Window... (just info for those who did not bother to read it...)

awe 2009-09-02 13:19:59

I think I would say "first time exception" means the exception was handled somewhere. Whether or not it was handled **properly** is a different question :) Particularly in code that's been around a while and upgraded to a different platform.

MarkJ 2009-09-03 17:05:49

Answer 2

+1 A:

I am not sure of what exactly is causing your exceptions, but if it is in your code and surrounded by catch blocks (that probably do nothing, other than swallow the exception), you can set Visual Studio to break on all errors, which should help you track the problems down.

In VS, go Debug > Exceptions... and you can check what type of exceptions it will break on.

Hope that is of help

Pondidum 2009-09-02 12:22:34

+1. In code converted from VB6 you also need to look for `On Error` statements as well as `try-catch`. Find the line in your project (if it is your code) where the exceptions are being thrown, and figure out what is going on. In VB6 there was no alternative but to trigger exceptions/errors for some common tasks, e.g. finding out whether a Collection contained a particular key.

MarkJ 2009-09-02 12:34:18

ansaurus

tags:

views:

answers:

A bunch of logged exceptions in Microsoft.VisualBasic.dll

related questions