.net框架Bace类库的代表图，以便更好地理解类型和成员合作
是否可以获得任何有代表性的图（例如对象图或类图） 来自名称空间的 .Net 类型。该图可以表示.Net类型和成员之间的关系和依赖关系，并且我们可以更好地理解命名空间部分的结构。而不是查看 MSDN 文本。
例如，我喜欢了解system.configuration命名空间重要成员的组织。
Is it possible to get any representative diagram (such as object diagram or class diagram)
from .Net types of a name space. The diagram could represent the relations and dependencies between the .Net types and members, and we could understand better the structure of portion of a namespace. instead of looking at MSDN texts.
For example, I like to know the organization of system.configuration namespace important members.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
嗨，
我找到了方法，它并不复杂：
1-创建一个 Visual Studio 项目，例如 console 或 winform 或 ..
2-在项目中添加类图
3-进入视图--->类视图，现在你可以看到类视图面板
4-扩展项目引用节点。
你可以找到你的项目引用它们的.net dll
5-现在将您最喜欢的 dll 拖到类图编辑器中
6-现在您拥有 dll 内部的高级架构
你可以选择重新排列它们并使用 dagram 进行炒锅
但有一点，我们似乎只能看到关联关系和
不幸的是，没有更多细节，例如聚合和......
我想一定有一些先进的工具
和有用的实用程序，可以增强图表的使用
太棒了，任何人都可以帮助并介绍他们
Hi
I found the way It wasnt Complicated:
1-creat a Visual studio project such as console or winform or ..
2-add a class diagram to the project
3-go to View--->class view,now you can see class view panel
4-exapand the Project refrence node.
and you can find .net dlls that your project refers to them
5-Now Drag your favorite dll into class diagram Editor
6-now you have a high level schema from inside of the dll
and you have options to Rearange them and wok with the dagram
but there is one thing,It seems that we could only see The Association Relation and
unfortunately thers not more details such as aggregation and ...
i think there must be some advanced tools
and helpful utilities that enhance working with diagram
its great anyone could help and introduce them
Microsoft 过去曾发布过 BCL 的（非 UML）概述（在 http://download.microsoft 上查找。 com），但这些一直都是非常高的水平。
实际上，BCL 定义的类型数量（更不用说整个框架）有数千种，因此超出了单个图表中更详细的内容。
Microsoft has published (non-UML) overviews of the BCL in the past (have a hunt around on http://download.microsoft.com), but those have always been very high level.
In practice the number of types that the BCL defines (let alone the whole framework) is in the thousands and therefore beyond anything more detailed in a single diagram.