Search code examples
visual-studio-2013code-map

VS2013 Adding Types to Code Map forces Rebuilding Projects

We have a large solution (112 projects) in VS2013 Ultimate.

I love the Code Map feature, however when I am dragging types onto a Code Map dgml it insists on building the solution - even though I have not made any changes.

I can't see many options for this great feature, but is there anyway to tell it to stop building the solution everytime I add a type to the diagram?

Solution

  • This is a known issue and major complaint with Code Map in Visual Studio 2013. It affects certain types of projects (like ASP.NET ones) more than others because these projects always report that they have changes and need to be rebuilt.

    The experience is improved in Visual Studio 2015 Enterprise, as we have added a "skip build" option.

    enter image description here

    We've made many improvements to CodeMap in Visual Studio 2015, so it's definitely worth getting it if you use Code Maps. Note that you can install VS 2015 along side VS 2013, so you don't have to migrate projects etc.