30 September 2005 16:45
, .NET 2.0
I've written enough code to start debugging and unit testing now (no flaming about writing unit tests first, etc, please!). The Create Unit Tests feature is really nice. With virtually no effort at all you can set up unit tests to start exercising your code.
One thing worth noting is that you can't have Code Coverage Analysis (which is very cool) enabled while your debugging tests.
The main purpose of this particular post, though is to raise an eyebrow of confusion over the debugging facilities. For as long as I can remember I've been able to Step In, Step Out, Step Over and Run to Cursor whilst debugging (Visual C++ had this and Visual Studio .NET too). However, my beloved Visual Studio 2005 seems to have restricted this down to just Step Over and Run to Cursor.
You can still set a breakpoint somewhere else and run to it, or find the method you want to step in to and choose run to cursor, but this is nowhere near as efficient or convenient as Step In and Step Out.
I'm hoping I just haven't found the right menu, toolbar or keyboard shortcut yet.
Update: I just found them! You need to customise your toolbar/menu to do it, but they are there if you look hard enough. Another one of those things that I hope doesn't stay like this when it's released.