First off let me say, I really like VS.NET and C#. I am getting 'real' work done with .NET and my team and I are happy on many levels.
But we are frequently frustrated with the integration of VSS. For example, try creating a class library in one project, and a web app in another project, and get them working in a solution and getting it all checked into source safe (without it creating .root
and _1 named VSS projects which you don't want or need) and then adding a new developer to your team.
Or try renaming a project in VSS and checking it back in (and spending hours trying to figure out the crypting binding error messages and warnings)
Or try connecting to work thru VPN and suffering the slowness of VSS over the net.
Am I making my point? If not, email me offline and I'll give you more examples...
Will we ever see version control technology from MS that's based on a 'real' server and with real-world distributed teams? Or is it sort of a second-class citizen there in Redmond and we need to keep looking at things like SourceOffsite, or entirely different
products, or should we just be content with VSS and suffer the sometimes frustrating integration with the dev tools we use.
What do Microsoft developers use day-to-day for version control? What do they use if the work from home?
Well, there's one very interesting source control provider I found (SourceGear Vault) that provides at least a FREE one-user license! It is built entirely with .NET, and is backed by a SQL Server or MSDE database.
I use it at home, as I do not want to pay oodles of cash for these things.
It implements EVERYTHING that VSS does, minus the ability to check in/out files in the visual merge.
However, one thing that REALLY needs to be done with SCP integration, is supporting renaming of files/projects.. It really sucks when I want to move files to a different directory/sub-folder.. I do it locally, then must open VSS directly and move them as well.
bshankle, I've started up a ProductFeedback wiki page just for Visual Studio, and populated it with some of your comments - please expand on them (or delete them, if you don't want them preserved for posterity and/or our devs!) as you see fit. Read more
about it here.
Comments have been closed since this content was published more than 30 days ago, but if you'd like to continue the conversation, please create a new thread in our Forums, or Contact Us and let us know.