As I sit here repeatedly waiting for the unit test for the C++ Single View Editor (the new scrubbed version of BscEdt) to build, I looked back through my blog posts after I joined the VS SDK team last July, and noticed that I've that I haven’t really blogged about Visual Studio Library (aka VSL)  very much.  My blog posts including mention of VSL can be summarized as follows:

  • 12/5/2005 – breaking changes primarily to the unit testing infrastructure.
  • 11/2/2005 – link to the official VSL feedback and suggestions thread on the VS Extensibility forum.
  • 9/13/2005 – note about VSL documentation status.
  • 8/12/2005 – one sentence about three classes VSL provides.


That is not a very impressive amount of content.  Looking at the official VSL feedback and suggestions thread I posted on the VS Extensibility forum, I see all I said about what VSL is useful for is:


“VSL is a C++ source library, primarily targeting the Visual Studio Platform, which extends the Active Template Library (ATL).”


Not very descriptive at all.


The official help docs on VSL are also pretty light on content, and the work item to add more comments to VSL keeps getting postponed.


Net result:  communication from us regarding VSL is crap.


I’ll start what will hopefully become a long series of blog posts on VSL today.