Today I published a new update to my Viasfora extension for Visual Studio 2010-2013. One of the new features in this build is a text editor margin that could be useful to other fellow developers working on extending the Visual Studio Text Editor.
One of the reasons why I implemented this was that I when I needed to extend Viasfora to support new file formats and other document types, I always had to resort to setting breakpoints in the debugger to figure out things such as the content type and how the editor worked, and this gets tiresome real quick!
In this first iteration, the margin exposes the following information:
Because the content type is the key to extending the text editor, it is very useful to be able to examine how the buffer graph is made up and making sure you don't have multiple instances of your extension on multiple buffers interacting poorly with one another.
- Exploring individual buffers: Besides visualizing the buffer graph, you can also explore the contents of the each of the buffers in a separate editor window. One side benefit of this is that it makes it easy to check out what the generated code for many text editors is like :).
- Exploring Content Types: In Visual Studio, content types can inherit from one another. For example, the "RazorCSharp" content type inherits from "Razor", which in turn inherits from "htmlx", and so on. With Viasfora, you can now easily inspect the content type tree.
- Keeping track of the caret position: Visual Studio does a nice job of telling you where you're located in the document at any given time with the line/column slots in the status bar. However, if you're implementing text editor extensions such as classifiers, you often will be tracking things based on the actual position in the text buffer, rather than as line/column pairs. The margin adds such a counter on the bottom right.
Eventually, I hope to add other useful features to the margin, but suggestions are always welcome. Enjoy!