Find out if we have memory leaks or overly generous memory usage.
Some areas to check: image export, clipboard handling, update diagram.

In the actual version, you see the inheritance hierarchy only if all types are on the diagram. If a type is missing on the diagram, the hierarchical tree is split in two as separated objects.

Suggestion : link related (as ancestor/child) types with a specific link type (providing some actions to see how many types there is between the two types, reinsert them on the diagram, etc.)

Like :
A <- B <- C <- D
A <****** D

Appveyor build should set the version number in source.extension.cs too.

It seems that every time I have displayed a class hierarchy and double-click a sealed class to open it in VS, the selection is always off by 3 chars.

Instead of the expected (using '|' as selection markers)
<tab>public sealed class |TypeName| : BaseName
it becomes
<tab>public sealed cla|ss TypeN|ame : BaseName

I have only seen it on sealed, but other keywords could possibly also be affected.

It happens when the tool window is floating and visible when starting up visual studio.

DiagramControl.xaml: ViewportResizeCommand="{Binding Path=ViewportCalculator.ResizeCommand}" is executed after tool window resize event so tool window size is not recorded in ViewportCalculator.

When add+resize gets processed together by the layout engine then everything is fine. But when the new node gets its position first (with zero size) and then gets its size, the viewport immediately pans to the enlarged node but later the layout engine will move it to the right.
Possible solution: translate the result of the layout engine to make exisiting nodes' position fixed.

It would be a very handy enhancement, if one could show the methods, fields and properties of a class in the quick diagram. It is already possible to show the description of the class, so replacing this text with the list of methods, fields and properties when the user clicks a "Show/Hide Details" button may be rather straight forward. This would make the quick diagram a UML class diagram that can be used to generate code documentation if needed.

Allow an option to display/hide the namespaces of types in the diagram. Hiding namespaces by default, as the tool does it right now, is OK. Sometimes I need to see namespaces displayed, as I have multiple types with the same name in different namespaces.

If the diagram layout changes then the misplacement gets fixed.
Very rare; must be some race condition. No repro steps known.

What expectation about VS2019 version of this exceptional and intuitive tool?
Thanks

With drag-and-drop and/or context menu.
Also add many files at once.

I don't want to add the classes one by one - there are too many. To get the idea about some new solution, I just want the tool to analyze whole solution (project) and build the diagram for me, including all relevant info.

Hi,
Please explain how to Uninstall this product, in the documentation.
I dont see it in control panel (Windows).
Thanks & Regards
Pilla Gurumurty Patrudu

Repro:

• Put QuickDiagram tool window into MdiChild mode (its tab is in the document well).
• DblClick a diagram node to go to source. The source code editor comes to the foreground and QuickDiagram tool window gets hidden.
• Switch back to QuickDiagram tool window by clicking its tab.
• QuickDiagram tool window comes to foreground in pan mode (it pans by following the mouse without holding down the mouse button).

It happened only once, no idea how to repro.

In Codartis.Util/Map.cs in line 30 there is:
lock (_dictionary)
maybe it should be:
lock (_lockObject)

The extension when installed from VS2015 tools->extension and updates options does nothing

Just sits. Anything that can be done to make it work?

The suspect is Diagram.HideRedundantDirectDiagramConnectors but we should profile to make sure.

The algorithm in HideRedundantDirectDiagramConnectors is very naive (finds all paths between all nodes). Try to find a better algorithm or move this task to background thread that will catch up eventually.

In a large C# project in VS2019, sometimes QuickDiagram tool is able to locate implementing and derived types, but most of the time it doesn't find any at all.

It makes no difference whether the class/interface is added to the diagram from its definition in source code, or from one of its references as illustrated above. Cleaning and rebuilding the solution does not make a difference. Restarting Visual Studio and reloading the solution do not solve it either. Manually locating and adding a derived/implemented type to the diagram will usually cause the QuickDiagram tool to discover their relationship, but additional derived/implemented types will remain missing, even if they are present within in the same csproj. I get the feeling it might have something to do with multiple classes/interfaces specified in the same source files but I can't say this with any certainty.

This is frustrating because it makes this extension almost useless.