.NET必备可视化调试工具（.NET Essential Visual Debugging Tool For Visual Studio）

1: Click to download: .NET Visualization Debugging Tool  (updated on 2016-12-29 19:11:00)

(Finally, it is completely compatible with some problems that cannot be used in the VS environment)

2: Execute after decompressing RAR: CYQ.VisualierSetup.exe will close the prompt window after success.

PS: Run once, support each VS version, improve the efficiency of debugging for life, and there is no side effect.

Open source address: https://github.com/cyq1162/CYQ.Visualizer  (2018-04-26 officially migrated to github)

Old address: http://code.taobao.org/svn/cyqopen/trunk/CYQ.Visualizer/

Subsequent upgrades get the address: https://github.com/cyq1162/cyqdata  in the documentation directory.

1: System.Drawing.Image: (this turn picture view)

2: MDataTable series: tables, rows, columns, structures

3: DataTable series: tables, rows, columns, structures

4: Generic series: Dictionary<,>, LinkedList<>, List<>, Queue<>, SortedDictionary<,>, SortedList<,>, Stack<>

5: Non-generic series: ArrayList, Hashtable, Queue, SortedList, Stack

6: Other inheritance from: Type of Enumerable interface: (too many types, future one-to-one test)

BitArray, ReadOnlyCollectionBase, HybridDictionary, ListDictionary, StringCollection, StringDictionary, BaseCollection, etc.

On the content of visual debugging, a search on the Internet, the relevant information is all the articles I have sent before, sad reminder on a word. . . .

It seems that no one is studying this piece, but fortunately, the sky is not worthy of the heart, or I am breaking through. . . . .

The process that can come out with such a simple tool is:

1: Once published a simple tutorial: Custom Visual Debugging Tools (Microsoft.VisualStudio.DebuggerVisualizers)

2: A different VS version of the DLL (Microsoft.VisualStudio.DebuggerVisualizers.dll) was collected.

3: wrote a tool, batch copy: open source release: VS code segment shortcuts and visual debugging rapid deployment tools

4: I thought of copying multiple project files to implement multiple VS version compilations (if I don't think of this, I guess it won't be tossed):

5: Solved the serialization problem (to support various types on a large scale):

By default, classes that do not support serialization do not support visualization. Therefore, if you want to support DataRow view, you will throw an exception directly.

In order to solve this problem, an Internet search (related information, the domestic is basically my own article, it is hard to find an article abroad).

Through research, this problem has finally been solved:

 Public  class EnumerableVisualizerObjectSource : VisualizerObjectSource
    {
        Public  override  void GetData( object target, System.IO.Stream outgoingData)
        {
            If (target is NameObjectCollectionBase)
            {
                Target = MDataTable.CreateFrom(target as NameObjectCollectionBase);
            }
            Else
            {
                Target = MDataTable.CreateFrom(target as IEnumerable);
            }
            Base .GetData(target, outgoingData);

        }
    }

Custom data source, when setting the data source, convert the object into MDataTable, and then go to the series by MDataTable.

6: MDataTable has to support and a large number of types of conversion work (the work of these years has been completed a lot, just need to complete).

When the last article was published, some netizens still couldn't understand what it was used for, a 唉~~~ word.

This time, under the full set of conditions, it took a day of research time and was directly written as a tool to share with you.

And you just have to download, and then double-click it, you have to get a good debugging experience!

In the process of developing and debugging, you can easily view all the data of the variables! ! !

Mom no longer has to worry about your debugging ability~~~

Don't ask me why~~~ I am not a mine under Lei Feng Tower~~~