I'm trying to write an extensibility add-in that will capture the source
control checkins and then do some pre-proccessing before checking the files
in. I do not want to use Visual Source Safe automation for this task.
I've figured out how to capture the checkin, but I can't find any way to
determine which files will be checked in. It might be a solution file, a
project file, or just a regular file. There may also be more than one file.
Can anyone help me with this?
Carlos J. Quintero [MVP] - 26 Oct 2004 13:34 GMT
I think that there is little support for source control operations for
add-ins, so you will have to use VSIP interfaces or VSS automation.

Signature
Carlos J. Quintero (Visual Developer - .NET MVP)
The MZ-Tools all-in-one add-in, now for .NET: http://www.mztools.com
> I'm trying to write an extensibility add-in that will capture the source
> control checkins and then do some pre-proccessing before checking the files
[quoted text clipped - 5 lines]
>
> Can anyone help me with this?
Tim Farley - 17 Nov 2004 20:59 GMT
> I'm trying to write an extensibility add-in that will capture the source
> control checkins and then do some pre-proccessing before checking the files
> in.
I know this might not help, but in Whidbey there is a new set of APIs to do
stuff like this. Look for the interfaces IPolicyDefinition and
IPolicyEvaluation in the extensibility documentation when the next CTP comes
out next month.
If you Google those interface names, you will find a few weblog posts that
talk about how to use them.
--Tim Farley