So, in other words - you aren't happy with it because it happens to come from M$? Obviously other products have used this standard - so it's not alone. Also, again - you can configure Studio/HS to use other tools via the command line. I think you are just being difficult now. Your original statement was that if you didn't use VSS, than the SC integration was worthless. That is wrong. The integration may not be perfect, but it certainly _does_ work with other products. ======================================================================= Raymond Camden, ColdFusion Jedi Master for Macromedia Email : jedimaster at macromedia.com Yahoo IM : morpheus "My ally is the Force, and a powerful ally it is." - Yoda > -----Original Message----- > From: thelist-admin at lists.evolt.org > [mailto:thelist-admin at lists.evolt.org] On Behalf Of Matt Liotta > Sent: Thursday, May 09, 2002 2:48 PM > To: thelist at lists.evolt.org > Subject: RE: [thelist] Dw MX concensus > > > SO in other words, Microsoft published an interface API that feature > matches VSS. You as a developer as welcome to implement that API for > your own source code control system, but much the API might not make > sense. > > VSS and CVS are very different from a methodology perspective. For > example, there is no such thing as checking in or out of a file. Thus, > offering this API doesn't really help me if I still have to use a CVS > client to do my work.