SourceSafe is not available in VS.NET when running on Virtual PC 2

Discussion:

(too old to reply)

Brian

2005-01-03 16:53:04 UTC

I have vs.net running on my Virtual PC along with sourcesafe. When I open a
solution that is under source control, I get the following message:

"The solution appears to be under source control, but its binding
information cannot be found. It is possible that the MSSCCPRJ.SCC file or
another item that holds the source control settings for the solution, has
been deleted. Because it is not possible to recover this missing infromation
automatically, the projects whose bindings are missing will be treated as not
under source control."

I am able to connect to the sourcesafe database existing on another server
in sourcesafe from my virtual session. The problem appears to be with Visual
Studio. When I go to "Tools/Options/Source Control/SCC Provider" in VS.NET,
the login ID is greyed out. Also, when I go to "File" in VS.NET, there are
no source control options. It does not seem to recognize the client
installtion of sourcesafe on my virtual machine. I installed sourcesafe
first and then VS.NET.

How can this be fixed?

Thanks,
Brian

Joe Masters

2005-01-05 04:59:25 UTC

Permalink

run ssint.exe to re-register vss and hopefully re-enable source control
integration. Then use File->Source Control->Open from source control to open
the solution.

Joe

Post by Brian
I have vs.net running on my Virtual PC along with sourcesafe. When I open a
"The solution appears to be under source control, but its binding
information cannot be found. It is possible that the MSSCCPRJ.SCC file or
another item that holds the source control settings for the solution, has
been deleted. Because it is not possible to recover this missing infromation
automatically, the projects whose bindings are missing will be treated as not
under source control."
I am able to connect to the sourcesafe database existing on another server
in sourcesafe from my virtual session. The problem appears to be with Visual
Studio. When I go to "Tools/Options/Source Control/SCC Provider" in VS.NET,
the login ID is greyed out. Also, when I go to "File" in VS.NET, there are
no source control options. It does not seem to recognize the client
installtion of sourcesafe on my virtual machine. I installed sourcesafe
first and then VS.NET.
How can this be fixed?
Thanks,
Brian

Brian

2005-01-05 21:53:04 UTC

Permalink

I made some progress. I did not have the ssint.exe file in my "Microsoft
Visual Studio\vss\win32" directory on my virtual machine. I brought it over
from my physical machine, and ran it on my virtual machine from the same
loacation. I then tried File->Source Control->Open from source control.
This is the message I get:

"There was a failure while initializing the Microsoft Visual SourceSafe
source control provider. You cannot use this provider to perform source
control operations."

I also got this message by going to Tools->Options->Source Control->SCC
Provider. This message popped up when I clicked on SCC Provider.

What else can I try?

Thanks,
Brian

Post by Joe Masters
run ssint.exe to re-register vss and hopefully re-enable source control
integration. Then use File->Source Control->Open from source control to open
the solution.
Joe

Brian

2005-01-06 22:05:05 UTC

Permalink

I found the problem. There were files missing from the "Microsoft
Visual Studio\vss\win32" directory. I copied all files from the win32
directory on my physical machine and ran ssint.exe and it now works fine.

Thanks,
Brian

Post by Brian
I made some progress. I did not have the ssint.exe file in my "Microsoft
Visual Studio\vss\win32" directory on my virtual machine. I brought it over
from my physical machine, and ran it on my virtual machine from the same
loacation. I then tried File->Source Control->Open from source control.
"There was a failure while initializing the Microsoft Visual SourceSafe
source control provider. You cannot use this provider to perform source
control operations."
I also got this message by going to Tools->Options->Source Control->SCC
Provider. This message popped up when I clicked on SCC Provider.
What else can I try?
Thanks,
Brian

Post by Joe Masters
run ssint.exe to re-register vss and hopefully re-enable source control
integration. Then use File->Source Control->Open from source control to open
the solution.
Joe

Joe Masters

2005-01-11 04:42:59 UTC

Permalink

Glad you got it figured out. Thanks for posting your solution back to the
group.

Joe

Post by Brian
I found the problem. There were files missing from the "Microsoft
Visual Studio\vss\win32" directory. I copied all files from the win32
directory on my physical machine and ran ssint.exe and it now works fine.
Thanks,
Brian

Post by Joe Masters
run ssint.exe to re-register vss and hopefully re-enable source control
integration. Then use File->Source Control->Open from source control to open
the solution.
Joe

Post by Brian
I have vs.net running on my Virtual PC along with sourcesafe. When I
open
a
"The solution appears to be under source control, but its binding
information cannot be found. It is possible that the MSSCCPRJ.SCC file or
another item that holds the source control settings for the solution, has
been deleted. Because it is not possible to recover this missing infromation
automatically, the projects whose bindings are missing will be
treated as
not
under source control."
I am able to connect to the sourcesafe database existing on another server
in sourcesafe from my virtual session. The problem appears to be
with
Visual
Studio. When I go to "Tools/Options/Source Control/SCC Provider" in VS.NET,
the login ID is greyed out. Also, when I go to "File" in VS.NET,
there
are
no source control options. It does not seem to recognize the client
installtion of sourcesafe on my virtual machine. I installed sourcesafe
first and then VS.NET.
How can this be fixed?
Thanks,
Brian