Here
is an odd behavior i'm experiencing with the new 2005 IDE in Visual
Basic. I have screenshots to prove this but I just noticed we cannot
add images to these posts, so I will try my best to explain the problem:
Recently, during debugging, as I step through code, the debugger seems
to "catch" exceptions on the weirdest places, but when I look at the
exception, nothing is declared. Let me explain with an example...
I have a line that goes like this:
Try
.
.
.
If dvView.Count = 0 Then
Exit Sub
End If
.
.
.
Catch ex as Exception
// Here I publish the exception
End Try
Now, I have a breakpoint set on the If dvView.Count = 0 Then. The weirdest thing happens, at this point, the dvView does have a count of 0, and I double check this in a watch window, BUT when I do a Step Over, it suddenly goes into my Catch block instead of the Exit Sub, and when I look at the exception, it says "ex is not declared".
In my catch block, I usually call a function which handles errors, so
I pass ex as an argument to this function, but in this case, ex is
never declared. What the heck is going on It's a perfectly valid
line of code. Can anyone help me understand what is going on
Restarting or rebooting never solves the problem. As well, I discover such new cases about once or twice a week and it does affect our application.

2005 IDE bug ???
c70070540
Hi there,
I've tried to come up with same code as you have above but It works as expected. Please provide more info, specially on how you do property get on count member of dvView class.
Thanks,
Daniel
Khushi2005
Alexey_Kiev