MindFill - Brian Carroll's Blog

Do While (WhatYouKnow) < (WhatYouKnow + 1)

Removing SourceSafe dependencies from a solution/project

Situation:
Your buddy has created a cool VB.NET application that you want to use.  He sends you the source code and it consists of a solution (MySolution) containing a single project (MyProject).  You attempt to open the solution and find that it has SourceSafe dependencies.  You need to remove all the VSS stuff from the solution/project files.

Solution:

1 - Go to the folder containing the solution files and delete the following:
          mssccprj.scc
          MyProject.vssscc
          vssver.scc

2 - Open MyProject.sln in your favorite text editor and remove the following section:
          GlobalSection(SourceCodeControl) = preSolution
                     ...
          EndGlobalSection

3 - Go to the folder containing the project files and delete the following:
          MyProject.vbproj.vspscc
          mssccprj.scc
          vssver.scc

4 - Open MyProject.vbproj in your text editor and remove the following lines:
          SccProjectName = "SAK"
          SccLocalPath = "SAK"
          SccAuxPath = "SAK"
          SccProvider = "SAK"

Now you can open the solution/project with no source control errors.

 

Posted: Mar 08 2004, 12:54 PM by bkcarroll | with 19 comment(s)
Filed under:

Comments

Jerry Dennany said:

Instead of editing the files directly, go to File -> Source Control -> Change source control. Here you can edit the Source Control Binding settings.
# March 8, 2004 3:39 PM

Brian Carroll said:

Sometimes it's the simplest things that slip by...Thanks for the short version.
# March 8, 2004 4:08 PM

Korby Parnell said:

The Change Source Control dialog box allows you to either Disconnect a solution temporarily--to work offline on your laptop, for instance--or Unbind, which removes the solution/project from source control. A little more information about this at: http://blogs.msdn.com/korbyp/archive/2003/08/20/54113.aspx.

The Unbind command only performs steps 2 and 4 from the manual edit procedure you document in this post. Your steps are quite good, by the way. I assure you that the metadata and scc "turd" files that Unbind does not delete are completely non-toxic ;-) and will not interfere with your ability to edit, build, or deploy the solution and its projects in any way.
# March 9, 2004 3:39 PM

TrackBack said:

# March 21, 2005 11:03 AM

Dan's Archive said:

# August 4, 2006 6:42 PM

Greg Thomson said:

Thanks for this, it helped.... I hate Source Safe

# July 11, 2007 8:23 PM

Arne said:

I hate Source Safe toooooo

# September 26, 2007 8:47 AM

theusualsuspect.com » Subversion said:

Pingback from  theusualsuspect.com &raquo; Subversion

# October 26, 2007 3:10 AM

Fred said:

Source safe really is a piece of CRAP!

# November 21, 2007 1:36 AM

Miggedy said:

Hi,

I'm having a problem with a solution that has three Visual C++ Projects and a VSS dependency I can't get rid off. VS2005 always asks while loading the solution if I want to permanently remove the dependency but selecting yes or no doesn't change anything. I also don't have a "Source Control" entry in the File menu.

I deleted all the files you mentioned, but I don't have any of the entries in the .sln or the .vcproj files and the message still keeps popping up every time I open the solution.

Any suggestions anyone?

Thank

  miggedy

# December 8, 2007 10:27 AM

Sourcesafe said:

More trouble than what it's worth most of the time.

I just look for anything that resembles sourcesafe (includes the text: 'scc') and kick it out

# February 7, 2008 11:59 AM

Lennard said:

Did you copy paste this blog from here?

www.knowdotnet.com/.../removefromsourcesafe.html

# April 23, 2008 9:00 AM

Murali said:

Thank, very helpful

# May 14, 2008 12:33 PM

KK said:

Mr. Lennard,

No matter what kind of projects you got, the process is going to be the same. It's like going to the guy sitting next to you in a restaurant and asking him why is he eating with his mouth just coz the rest of the restaurant is doing so too!

# May 27, 2008 1:03 PM

Steve said:

For you guys saying that you hate SourceSafe. Trust me, once you work in some other source control programs (namely, TrueChange), you'll think SourceSafe is the best thing that ever happened to you. I just moved from a project that used TrueCrap... er... TrueChange to one that uses VSS, and I am thanking the .Net gods.

# June 6, 2008 2:20 PM

larker1 said:

""Instead of editing the files directly, go to File -> Source Control -> Change source control. Here you can edit the Source Control Binding settings""

This only works if everything in your project is set up exactly the way Microsoft thinks it should be.  I'm migrating a .net 1.1 project from VSS 6 to TFS 2008.   A) TFS 2008 does not like .net 1.1 projects, it forces you to reset the source control bindings on every project in the solution the first time you open in.  B) In the case of  web services and other web projects that require a local map to a virtual directory, the process is even more painful. In my solution, after presenting me with the Change Source Control window and telling me  to select a directory, it absolutely refuses to allow me to select the appropriate folder.  At this point I HAVE to edit the files manually.

# September 4, 2008 6:00 PM

Roaming in the computer world » Blog Archive » Manually remove Visual SourceSafe control from a solution said:

Pingback from  Roaming in the computer world  &raquo; Blog Archive   &raquo; Manually remove Visual SourceSafe control from a solution

# January 27, 2009 11:47 AM

Ezeamama Andrew said:

Thanks Brian Carroll this solved my problem.

# May 14, 2009 10:36 AM

Alfredo De Regil said:

Thanks for this manual solution. Sometimes I need to open a visual studio solution on a computer that does not have the visual source safe installed so this manual option is what I really needed.

# September 15, 2009 10:50 AM
Leave a Comment

(required) 

(required) 

(optional)

(required)