Attention: We are retiring the ASP.NET Community Blogs.
Learn more >
Namespace Management
With all of the new classes in 2.0, I sometimes find myself guessing at the dll's in order to find out how to reference them in a project. Case in point: with the MONAD namespaces (System.Management) , I didn't realize that they were actually found in the “Program Files\Longhorn Command Shell Preview” folder. Another point (from 1.1), the System.ComponentModel.Design namespace is actually held in System.Design.dll. I was recommended to use Reflector to search for the classes, but what about classes that are not included in the framework?
3 Comments
Even more unintuitive is the fact that the System.Web.UI.Design classes are also in System.Design.dll, which is not referenced by default, even if you add a Web Custom Control. Makes me very glad that the design-time story for controls gets so much better in 2.0. :-)
>but what about classes that are not included in the framework?
You just open the file in Reflector.
Point is that there's not a central location to just go open up a DLL. Even with reflector, you need to know the location and which DLL to open to find your Class/Method.