I presume that this is why Microsoft promises lots of 'Team productivity' enhancements in their next version of Dot Net. (Funny how it's always going to be great in the next version.)
Our teams have been frustrated not just by SourceSafe, but all of Microsoft's tools. Each new iteration is more complex, unecessarily interdependent with other MSFT products, and buggy. (SourceSafe's penchant for corrupting the very thing it purports to protect comes to mind.)
Thanks for the links to the other source control tools--I'll check them out.
You're right. I should have provided references to CA and MSFT. I assumed in this context that it would be obvious--neglecting to consider the broader audience that this site reaches.
Jeff
Slashdot Mirror
I presume that this is why Microsoft promises lots of 'Team productivity' enhancements in their next version of Dot Net. (Funny how it's always going to be great in the next version.)
Our teams have been frustrated not just by SourceSafe, but all of Microsoft's tools. Each new iteration is more complex, unecessarily interdependent with other MSFT products, and buggy. (SourceSafe's penchant for corrupting the very thing it purports to protect comes to mind.)
Thanks for the links to the other source control tools--I'll check them out.
--Jeff
You're right. I should have provided references to CA and MSFT. I assumed in this context that it would be obvious--neglecting to consider the broader audience that this site reaches. Jeff