Compartilhar via

Answers to Your SourceSafe Questions

  • Artigo

An email arrived in my Inbox recently from a customer that read,

“I've got ALOT of questions, and I hope you could help me...

  1. How do I use Shadowing in .NET?
  2. How can I force users to check in their files and log out of SourceSafe so that I could lock the DB?
  3. How can I split a DB?

Help needed ASAP please! Thanks dearly!”

Dude, you came to the right place. 

In general, if you have questions about Visual SourceSafe, you can see everything I've ever published on the subject in my blog by clicking the Visual SourceSafe category on the right hand side of my blog page. On the page that appears, scroll to the bottom of the main frame and click Full Visual SourceSafe Archive.

For answers to your questions:

  1. How do I use Shadowing in .NET?
    See, SourceSafe Shadow Folders, Maintaining Synchronicity.
  2. How can I force users to check in their files and log out of SourceSafe so that I could lock the DB?
    See, End-to-End Analyze Script for Keeping a VSS Database Healthy (user ejection seat not included).
  3. How can I split a DB?
    See, How To: Split a VSS Database into Two or More Databases

++++++++++++++++++
This posting is provided "AS IS" with no warranties, and confers no rights. Microsoft kann für die Richtigkeit und Vollständigkeit der Inhalte in dieser Newsgroup keine Haftung übernehmen. Este mensaje se proporciona "como está" sin garantías de ninguna clase, y no otorga ningún derecho.

Comments

  • Anonymous
    April 07, 2004
    Question: does microsoft use vss for source control? it doesn't seem to be able to handle large loads of programmers
  • Anonymous
    April 09, 2004
    We're using VSS on a project and were wondering how VSS decides if a file is binary or not? If it asks Windows, do you happen to know how Windows decides this?
  • Anonymous
    April 19, 2004
    Hi Korby.

    I have a question re the solution root folder:

    I recently set up a build/source control environment for client - new to both .NET and VSS (and source control in general).

    I based my approach on the Team Development whitepapers on MSDN (I wanted as standard an approach as I could get), and prior experience at Microsoft.

    Unfortunately, I was using VSS 6.0c and, for this reason (I think) the "solution.root" functionality wasn't apparent. My clients, of course, have fresh installs of VS 2003 and VSS 6.0d.

    Now the question is whether I should revise the entire approach to work with the default solution root behavior, or recommend turning it off.

    I'm leaning toward the latter because it still seems like a better approach to me to start with a blank solution, and create a symmetrical folder structure on the dev machine, in SourceSafe, and - in our case - on the build server as well.

    Our current approach - which is right out of the MSDN whitepapers - overrides default Visual Studio behavior that occurs when you create a new web application - we create the vdir ahead of time, and force the project files on the dev machine into the shared, symmetrical folder structure. It doesn't appear that the root folder approach accomplishes this?

    What do you think?

  • Anonymous
    April 19, 2004
    The comment has been removed
  • Anonymous
    April 19, 2004
    The comment has been removed
  • Anonymous
    April 26, 2004
    Can I rollback a entire project to a specific label? It seem the rollback only work on one file.
    Ok I can use the trick: checkout, delete, get old version, check-in. But the history (and comment) are not updated.

    Thanks
  • Anonymous
    April 27, 2004
    Is it possible in Visual Studio.NET to hook up to two or more projects from separate source safe databases in one solution file ?
  • Anonymous
    July 14, 2004
    Is anyone aware of a utility out there that can check VSS files in and out through the Windows Explorer? We have some files controlled by VSS but not wrapped up within a VS.net project and traversing the project tree in VSS' IDE is time consuming. It would be nice to be able to right-click a file and check-in/out for quicker access. Thanks for any pointers...
  • Anonymous
    July 14, 2004
    They do exist. Some are in active development. All are third party projects. They're often referred to as namespace extensions. When WinFS ships, Windows Explorer-based file versioning will be truly possible. IMHHHO, the existing implementations I've used are somewhat kludgey and hacked together.

    Can somebody out there point to one or two?
  • Anonymous
    July 08, 2005
    The comment has been removed
  • Anonymous
    August 18, 2005
    Very nice blog. It is very helpful. http://www.bignews.com
  • Anonymous
    March 19, 2006
    Very nice and informative website.
  • Anonymous
    April 29, 2006
    Very nice website with a lot of informative response from members
  • Anonymous
    August 22, 2006
    I like this blog.
  • Anonymous
    September 01, 2006
    Hi baby!
  • Anonymous
    December 15, 2006
    We are planning to use SS2005 for these operations. We are having a different model of development. We have a product (solution) which will be the base code for everyone. When we install the product to a customer, we are planning on creating a new solution named after the customer. All the solution files from the base will be shared with the customer solution. At times, we'll be making some custom changes which are exclusive to a customer. At this time, we want to branch the required files to the customer solution. Now, my questions are
  1. When we fix an issue in the base code, how can it be rolled out to all the customer solutions?
  2. When we want to upgrade the product (new release), should we create a new solution all together or just label the current build before making new changes?
  3. Will we be able to use VS2003 based solutions in SS2005?