I have been trying to use VSS integration with VS.Net for well over a year. It works great at home when I am by myself. I can track changes and keep versions in history and can confidently change code knowing that I can roll back if I have to. At work, however, when it is critically important, the integration has limitations that result in having to use VSS explorer outside of VSS.Net.
I have come to very few revolutionary conclusions. I was hoping to get to a point where I could recommend a configuration for a large development team. Unfortunately, I can only express that for those who wish to use it, VSS integration is tolerable.
First off, only bind what you will be editing. If you aren't going to be changing a project that is part of a larger solution, get the files from source control and use them locally but don't bind them to the VSS location. If you don't need the source code at all (for debugging or stepping through funtionality) simply get the binaries and use the compiled dll. Its much easier and saves a lot of time when getting latest.
For a project that you do modify and require VSS functionality, here are some tips:
Its cumbersome but marginally useful. Its like a cup holder that doesn't really hold any cup well (my Acura) but is better than no cup holder at all (my Westfalia)
That's all I have for now, if I think of anything else, I'll let you know.
Remember Me
Theme design by Jelle Druyts
Pick a theme: BlogXP calmBlue Candid Blue dasBlog Discreet Blog Blue Elegante essence Just Html Mono Movable Radio Blue Movable Radio Heat orangeCream Portal Project84 Slate Sound Waves Tricoleur
Powered by: newtelligence dasBlog 1.8.5223.2
The opinions expressed herein are my own personal opinions and do not represent my employer's view in any way.
© Copyright 2008, Rusty Zarse
E-mail