spelunking through my local disk trying to find where Visual Studio .NET stores theseitems, but to no avail. Perhaps they are in some mystery binary blob, or hidden deepin the registry encoded as GUIDs. Or perhaps, they are sent off as SOAP packets tothat mysterious internet “cloud” Bill Gates keeps talking about. Regardless, I wouldhardly use this feature as an industrial strength code repository. (What happenswhen you re-install Visual Studio .NET or move to another computer? Where do yoursnippets go?)Finally, remember that all code repositories are potential bug factories. If you pastein buggy code and re-use it, you are cloning bugs. And this inevitably leads tofascinating new strains and variants of defects which are likely to be un-fixable.
Control Minus Takes You Back
I was programming in Visual Studio .NET for over 6 months before I discovered thisone, and it is one of the most useful navigation keys there is. To “Go Back” (in otherwords, return to the previous position before you navigated away) simply press Ctrl-Minus. This works across windows, and the navigation buffer appears to be limitless,so this is a great replacement for the old VB Ctrl-Shift-F2.
Dock the Class View to the Left of Code
Call me slow, but after a class I’m writing reaches over 100 properties and methods,I can no longer get a quick handle on how it works. Although using Regions in codemakes code expandable and collapsible, that can only go so far. One neat trick I’vefound is to dock the Class View toolwindow directly to the left of my code window.The Class View then acts as a table of contents for me as I work on the code.