SourceSafe Team's WebLog

The very first post: Welcome Everyone!

Welcome to the SourceSafe Team's blog!
 
The mission for this blog is to serve as a link between the community of SourceSafe users and the product development team who works on this great product every day. We truly hope having this space can help improve your experience using our product, and at the same you can help us with your feedback to improve the future versions of SourceSafe.
 
Expect to see posts about once per month on a variety of topics, from tips & tricks, to best practices, to discussions of upcoming features in Visual SourceSafe 2005.
 
On this very first post from the team we would like to recognize the amazing work of Mark Michaelis and Korby Parnell have done to get SourceSafe information out in the community. They are our first links in our Community Resources, where we are compiling links to interesting web resources available for SourceSafe. If you have your own site/blog/faq about SourceSafe and would like us to link to it, please let us know.
 
This is a team blog and you will be seeing posts from the developers, testers, program managers, and designers who work on Visual SourceSafe.
 
We hope that you find it interesting to read and to get to know us.
 
[Alfredo]
Ohh, btw, my name is Alfredo Mendez. I am a Program Manager in the SourceSafe team. I started on the SourceSafe team in 2002, at the early stages of planning of SourceSafe 2005; and I am amazed at all that this team has accomplished over this period, I will get into that in another post :). I have been at Microsoft since 1998, first at Microsoft Consulting Services in Venezuela and in 2000 transferred to Redmond to work in Visual Studio.

 

Published Wednesday, June 23, 2004 11:00 AM by CheckItOut
Filed under:

Comments

 

pemo said:

I'm real interested in algorithms that 'spot the differences' in text (and, after all, that covers code) - what do you guys use here - is it just SCCS-rooted stuff, or are there better algorithms out there that you use?

Ta
June 23, 2004 11:46 AM
 

Mark Michaelis said:

Thanks for the kind words Alfredo. Please note that both Joe Masters and Weston Morris (the other VSS MVPs) also contributed significantly to the FAQ.
June 24, 2004 1:19 AM
 

Chad Myers blog said:

June 28, 2004 12:29 AM
 

Visual SourceSafe 2005? Why? said:

Trackback
June 27, 2004 9:32 PM
 

Chad Myers blog said:

June 28, 2004 10:21 AM
 

Dmitry said:

Pemo,

There is an interesting algorithm I know about: "An O(ND) Difference Algorithm and its Variations" by Eugene Myers. You can find it for example here: http://www.xmailserver.org/diff2.pdf

Dmitry.
June 28, 2004 12:08 PM
 

Steve Nield said:

When are you going to prevent those VS .Net app devlopers including VSS bindings in the .Net solutions that give us users so much hassle when trying to migrate code from one VSS archive to another?
June 29, 2004 3:47 PM
 

Rich Knox [MS] said:

VSS2005 makes it much easier to deal with solutions with obsolete SCC bindings. A simple dialog allows you to ignore the SCC bindings. The Change Source Control dialog is also easier to use.
June 29, 2004 4:24 PM
 

Steve Nield said:

The problem isn't obsolete bindings - it's that solution files contain hard coded references to the VSS bindings. Say we have a solution in $/Steve/Dev/DummyProj.sln and we want to continue working with this archive for ongoing dev work but also need to maintain a live code base, e.g. $/Steve/Live/DummyProj.sln which may need building and deploying whilst the next iteration of Dev is going on. Try copying the source files from one tree to another and you'll see that the VSS bindings are stored up within the .sln and .proj files??? There's no need for any hard-coded binding within these files - by all means create some .vsssccsssccss files to store this info and then read them in when loading the project but at the very least they should be configurable and/or be able to deleted and re-created pointing at the archive structure I choose.
July 2, 2004 6:23 PM
 

Alin Constantin [MS] said:

Steve,

it seems to me that you're using an older version of SourceSafe or at least you don't have a correct list of project extensions set.
You should open SourceSafeExplorer, go to Tools/Options/FileTypes/CreateSccFiles and add into that list the extensions of the projects you're working with. Do that for all team members.
Then, open the solution in VisualStudio, unbind it and rebind it back, checkin the changes and for rest of the team do a Get.

If everything is done correctly, the solution and projects should not store $/ paths, but instead some dummy-SAK locations that will just tell us the projects are controlled.
The real $/ bindings will be then persisted by the VSS provider in the msccprj.scc file, and they will point to the archive structure you choose.
July 2, 2004 6:46 PM
Anonymous comments are disabled

This Blog

Syndication

News

Welcome to the SourceSafe team blog !
Disclaimer

© 2008 Microsoft Corporation. All rights reserved. Terms of Use  |  Trademarks  |  Privacy Statement
Microsoft
Page view tracker