![\"clip_image002\"](\"https:\/\/devblogs.microsoft.com\/00\/00\/00\/45\/92\/metablogapi\/4338.clip_image002_09633A82.jpg\" "\\"clip_image002\\"")
<\/a><\/p>\nOK, but I need more than one Code Map… <\/h3>\n
In Visual Studio 2013, you can create a Code Map by selecting Directed Graph Document<\/b> in the New File <\/b>dialog, from the Architecture<\/b> menu, or by choosing Show on Code Map <\/b>in Architecture Explorer, Solution Explorer, and the Debugger tool bar. However, it\u2019s difficult to start a new and less cluttered Code Map to focus on specific components in an existing Code Map because Show on Code Map <\/b>always adds code elements to the most recent Code Map. Meanwhile, the New File <\/b>dialog and the Architecture<\/b> menu just create a new blank Code Map without any styles. <\/p>\n
In Visual Studio 2013 Update 3, we added the capability to drag arbitrary binaries from Windows File Explorer into a Code Map in order to understand their dependencies, and to try to componentize them. Of course, creating a new Directed Graph Document is a pre-requisite for this\u2014which is also quite difficult to do. Many users found it hard to discover the options for creating a new Directed Graph Document, or became confused when prompted to create a new Modeling Project.<\/p>\n
In Visual Studio 2015, both of these problems go away. We\u2019re providing some new ways to create a Code Map that makes the feature easier to use, and\u2014by removing unnecessary clutter\u2014even more useful.<\/p>\n
A day in the life of a developer \u2026<\/h3>\n
Imagine that this is my first day with the team that produces Entity Framework (EF), and I\u2019ve been given the simple task of adding a new command line option to the Migration tool. I’ve opened the EntityFramework solution, and generated a Dependency Graph using the option in the Architecture<\/b> menu. This helps me to orient myself within the code, and I\u2019m pleased to see that migrate.exe<\/b> depends only on EntityFramework.dll<\/b>. Immediately I know that I don’t have to examine the other projects. <\/p>\n
Looking at the files in Solution Explorer I notice that the Migrate project contains a file named Program.cs. This will be my starting point, and so I select Show on Code Map<\/b> to add it to the existing map.<\/p>\n I can see that Program has dependencies on Entity Framework.dll and on Externals, but the diagram is becoming more complicated and I still need to know more. So I expand Program<\/b> to examine its contents, and the diagram now gets really cluttered. It contains many things that I’m not really interested in.<\/p>\n And every time I expand an item, the graph gets bigger and interaction with it becomes slower and more difficult. That’s not what I want. I want to keep the overview map (this helps me to stay oriented with the overall solution structure), but I also need to create a new Code Map. In Visual Studio 2013, I can try to find out how to do this using the Quick Launch box, but this doesn\u2019t show anything useful.<\/p>\n Next, I try \u201cDGML\u201d because I noticed that this is the extension for the map files, but that shows nothing either. So I use the Add New Item<\/b> option on the Projects<\/b> menu, but entering \u201cCode Maps\u201d or \u201cDGML\u201d in the search box again finds nothing.<\/p>\n In the end I ask my colleague, who tells me that I need to create a new \u201cDirected Graph Document\u201d in the Add New Item<\/b> dialog, or use the New Diagram<\/b> option on the Architecture<\/b> menu\u2014and that forces me to create a Modeling Project that I don\u2019t really want. It also gives me a new blank Code Map where I have to add the items I\u2019m interested in. <\/p>\n In Visual Studio 2015, I can reduce the clutter without losing my existing high-level diagram of the solution structure or starting with a blank map by creating a new Code Map that contains only the selected items in the current Code Map. I simply select the components I\u2019m interested in and choose New Graph from Selection<\/b> in the short-cut menu.<\/p>\n Now I have a useful and uncluttered diagram focused on just the items I want to explore. I expand the migrate.exe<\/b> item to see that it contains a Program<\/b> item that depends on EntityFramework.dll. <\/p>\n I dive deeper by expanding the Program<\/b> item to see its contents. It\u2019s now clear that the object I need to work on is the CommandLine<\/b> class.<\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\nThe answer: new graph from selection!<\/h3>\n
<\/a><\/p>\n<\/a><\/p>\n