VB.NET Whidbey – Debugger wants your class constructor!

This is probably old news to many who have been playing with VB.NET Whidbey for a while…

I noticed that when debugging, if I didn’t have have NEW in a custom class, the debugger stops on code that instantiates that class, givint a little popup message “There is no source code for the current location.” You can hit okay and then just continue and all  is fine. This is not affected by Option Explicit or Option Strict settings.

Probably something that has been duly noted by now. I wish I had time to do this stuff this summer when it would have been useful for the VB team.

  Sign up for my newsletter so you don't miss my conference & Pluralsight course announcements!  

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.