There are a number of features in the product that completely depend on the source code you push through the feature in regards to memory utilization and performance. For example, the creation of the “Standard Graphs” ( any of the graphs generated by the following menu items


) can be a very fast operation or can take some time and use some significant amount of memory, depending on how large your solution is.

We have lots of internal tests and code bases we run the product against, but I would like to hear how the product is performing against the code you are putting it up against.

Please drop me a note and let me know what your experiences are now that the Beta2 build is broadly available. I want to hear the good, the bad, and the ugly! Don’t hold back! 🙂



Comments (6)

  1. phikaa says:

    Is “Generate Dependency Graph ” the VS2010’s new feature?

  2. Hi Cameron,

    I will try on my current project at work next week (~120,000 lines of code).

    Which information would you like to know? Only the necessary time to generate diagram?



  3. Right. The "Generate Dependency Graph" pull-right gives you the "By Assembly", "By Namespace", "By Class", and "Custom…" options. Those menus result in DGML diagram generation based on the solution currently loaded in Visual Studio 2010.

  4. Yes, would love to understand time to get the graphs, memory used, is the perf after generation feel good, etc.

    I’d also like to understand the general characteristics of your application, whether it is C# or VB, web app vs. client side, that sort of thing.

    Feel free to ping me directly at

  5. Iv tried generating Depency grpahs by assembly and by namespace for a 120 000 lines of code solution, It tok about 3 minutes, witch is faster then I expected. The main problem for me everything in my solution is included in the graphs, I cant filter anything, instead I I get to much information, so I have to spend much more time removing namespaces and clases I dont want in the graphs. (for example a namespace with just Typed datasets, witch generates about 2000 classes)

  6. Mattias, I’m going to be putting up a post or two about this exact issue. Essentially, you need to use the Architecture Explorer and the DGML graphs in concert to break down your graphs.

    Again, I’ll post here shortly as this has been a common request / question.

    Glad to hear that the product is performing well on your solution! 🙂