visual-sourcesafe

Is there a way in Microsoft Visual SourceSafe to see all the files I've ever checked-in? With a project selected, go to Tools, Show History, tick Recursive, and enter your user name into User. Click OK. The command line may be faster, more efficient for this. From the command line: cd C:\Program Files\Microsoft Visual SourceSafe SET SSDIR=<path to folder containing srcsafe.ini> ss Status $/ -R -U<username> > checked-out-by-username.txt And then check the contents of checked-out-by-username.txt for your check-outs. For example: My srcsafe.ini was in C:\Program Files\Microsoft Visual SourceSafe

Is there a way to export files/folders from Source Safe? (i.e. getting rid of all .scc files, just like SVN export) Just do a regular get, then run something like ATTRIB -R *.scc /S DEL /F /S /Q *.scc The first command removes the read only flag from those files. The second deletes everything that matches *.scc along the path. 来源： https://stackoverflow.com/questions/1069133/export-from-source-safe

How can I create a New project & Solution in the same, existing , directory? No matter what I do, it keeps creating a new (sub)directory for the project and populating that directory instead of the one(s) that already exist. I have the "Create directory for Solution" checkbox cleared so that it will put the solution an dproject in the same folder and not create a solution folder, but it still keeps making the project sub-folder. How can I fix this?!? This has bugged me for a long time, but I've been able to ignore it or work-around it up until now. But now it is kicking my butt productivity

I tend to get the feeling that most folks here think SVN is gold-plated goodness, whereas VSS is the worst program ever devised (at least as Version Control is concerned). That said, why? I've used some CVS, and my current job uses VSS, and from a grunt on the team's perspective, I can't really tell that much difference. Most of the differences I've seen are cosmetic. Granted, I've not tried to do any branching/merging in either, but as a coder who comes in, checks out files, works on those files and checks them in at the end of the day, why would I want 1 over the other? “Visual SourceSafe?

I've just joined a new company and at the moment we're using Microsoft SourceSafe as our repository. The settings aren't ideal and it's proving to be a big pain in the neck. I've recently used Mercurial and thought it was amazing, so I'm advocating switching to that, but it looks like the company already has a Team Foundation Server licence and wants to use that instead. Can anyone give me a list of points where one is better than the other? I've not used TFS and so I don't know what it's good/bad at. VonC You cannot directly compare TFS and a DVCS. If your company leans toward TFS, that may

I have the opportunity to give a formal presentation to my boss about anything that benefits the company. My idea is to adopt source control in my workplace. I have been using Mercurial to manage my own project at work, but the rest of the team does not have a formal source control system in place. Unfortunately, I'm not very good at presenting ideas. So, can you guys tell me why developers MUST use source control? Additionally, why would you choose any tool except Visual SourceSafe? I don't have experience using VSS, but he is likely to ask why we wouldn't just use Microsoft's tools. I want

After doing some search on SO, Google and MSDN forums I've become frustrated that there is so little information for what might seem like an obvious question and possibly a dumb question. I need to use source control in Visual Studio 2010 Professional. I do not have separate Team Foundation Server 2010. Some people have mentioned SourceSafe? I haven't seen any SourceSafe inside of the Visual Studio 2010 to be honest. What are some alternatives (preferably free) for source control in Visual Studio 2010? Or is it already integrated in Visual Studio 2010 that I am so blind to have missed that?