Not exactly, but you can still interact with source control via VS.net:
VS.Net does define an API for interacting with VS.Net projects. If the
target project happens to be in source control, you seem to get the source
control interaction automatically.
Example:
I have a code generator that can create a lot of wrapper classes for
accessing tables in a database. The generator is a VS.Net plugin. When I
added project automation (so that it automatically adds the files that it
generates to the open project in VS.net), I found that I VS.Net
automatically handled some of the source control issues (like checking out
the project prior to adding the files, etc.
I expect that the interation that you get automatically will pretty much
follow the interaction that you get when you interact with a project or
files in the IDE. If you need more than that, VSS exposes that
funcationality via COM objects.
"Sam" <sa************ **@intel.com> wrote in message
news:D9******** *************** ***********@mic rosoft.com...
Does anyone know if the .NET Framework defines a set of classes that allow
you to access Visual Source Safe within your C# programs.
I know there is some type of COM interface
(http://msdn.microsoft.com/library/de...-us/dnvss/html
/vssauto.asp?fra me=true) that allows programmers to access Visual Source
Safe from a VB or C++ app, however; I hoping to avoid accessing
non-managed code from my C# apps.