can anyone tell me what will be new in sourcesafe in the whidbey version ?
well, I saw that sourcesafe in whidbey got something for Internet also.. so I guess that we will be able to do internet source safe also.. I was missing this feature a long time ago.. I am not sure that its exactly what I am looking for.
Does anyone know if there will be branching support in the new Visual Source Safe version ?
I sure hope so.. the "tagging" ability of CVS would be a nice addition to SourceSafe IMO. I've often encountered the need to create a "test snapshot" of a repository that is accesible through the vesioning software. Caveat: I am not confident that my experience
with VSS is sufficient enough to warrant that it doesnt allow me to accomplish what I point out.
focuses on the new features under development for the existing Visual SourceSafe product that will be released along with Visual Studio® .Net codename "Whidbey.The webcast will consist of a series of live demos of these new features, including: SourceSafe Web
Service Configuration, Remote Access via HTTP, Performance Improvements, Globalization, Visual Studio Integration: Rename/Deletes, File Dialogs, Asynchronous open.
will look at it next week.
I sure hope so.. the "tagging" ability of CVS would be a nice addition to SourceSafe IMO.
Say J: Have you tried the Label command in VSS? This allows you to name a version of code just like the tagging in CVS (I think - it's been a couple years since I've used CVS ).
Sometime in the future you could pull code by label to recreate a specific version of something you might have shipped. You can also list differences between two labeled versions. Korby
posted a script from a newsgroup user to do this. I have some experimental C# code to do the same here (in Longhorn!).
Awesome.. thanks for pointing it out. I was pretty sure that I just didn't know how to do this, hence my cover my arse clause
"Hatteras is a spicy new SQL Server-based, fully transactional, client-server source control system that will blow your socks off."
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.