VSS integration with VS.NET

[news.microsoft.com]

Hi,

I installed the VSNET IDE and then later i installed the VSS 6.0c and
while I have it configured correctly the right click context menu on the
source explorer does not show source control options, anyideas`? I do not
intend to reinstall the IDE as its bloat and takes ages.

Is there an easy way to fix this? Ive got 2002 and ive seen this on 2003
also.

Why no checkin /out etc options on the context menu?

 

[Larry R.]

You need VSS 6.0d. Then the project needs to be added to VSS using the IDE
File/Source Control menu.

Cheers,
Larry Rebich

 

[news.microsoft.com]

So, this is a bug fix for vs.net? or a new addition?

 

[news.microsoft.com]

MSDN only has 6.0c as the latest it says and sp6. Tried that. Still doesnt
work. It did before.

Ive checked the Source Control Provider settings and theyre the same.


In MS's own words...

"Visual SourceSafe 6.0 Service Pack 6, containing the latest version of the
Visual SourceSafe product (6.0c), is now available for download"

There is no 6.0d apparently

 

[Jason Wilden]

There is definitely a 6.0d (build 9848) version of VSS - I have it on my
machine and presumably it shipped with VS.NET 2003. Try making sure that
the VSS SSAPI.DLL is registered correctly on your machine.

 

[news.microsoft.com]

Well, im on 2003 and its 6.0c and MS web site says 6.0c is the latest.

 

[ozbear]

Well, im on 2003 and its 6.0c and MS web site says 6.0c is the latest.

<snip>

6.0d is the latest, and is what you should be using.
It came on my MSDN subscription.

Oz

 

[news.microsoft.com]

Its what I have and its not on the web download and I dont have MSDN.

Its a bug, deal with it.

 

[ozbear]

Its what I have and its not on the web download and I dont have MSDN.

Its a bug, deal with it.

If you feel that it is a bug, upgrade to 6.0d.

 

[Martin G. Brown]

If you have Visual Studio 2003, Source Safe 6.0d came bundled with it. Try
looking on the DVD/CDs it came on. On my DVD it is in D:\VSS\SETUP.EXE. For
some reason 6.0d is not available on the internet. By the way it is not part
of the standard VS 2003 install, it has to be run separately.

It still ought to work with 6.0c though.

Martin
http://www.mgbrown.com

 

[news.microsoft.com]

I have 6.0c thats what I got, thats what it installed, I dont have MSDN.
which part of that don't you understand?

*gets his clue bat*

MAKE THE PATCH AVAILABLE ONLINE THEN I CAN UPGRADE

 

[Martin Brown]

What I don't understand is where in my previous post did I mention MSDN?

You have said in a previous post that you had Visual Studio 2003. Visual
Studio 2003 and Visual Studio 6.0d come on the same disk. If you have one
you have the other. No need to "MAKE THE PATCH AVAILABLE ONLINE THEN I CAN
UPGRADE" as you should already have it on disk. I thought my post made this
clear.

You might also want to try checking your project's Source Safe bindings. You
can do this by selecting the File -> Source Control -> Change Source Contol
menu item. This brings up a dialog with a list of project in. You should
have an entry in the Server Binding column and a tick in the connected
column next to each project. If you don't try selecting the project and then
using either the connect or bind toolbar buttons to conect to the source
safe database.

 

[news.microsoft.com]

Well I installed VSS and also 2003 and i got guess what, 6.0c and as for the
MSDN refereral, that was for other people going around crying and waving
theyre MSDN subscriptions blurbs.

Why not have a patch available online if its a known bug. Oh yeah I have to
spend how much to fix a little bug? Get real.

The issue is, it worked before and it doesnt now since I upgraded, Its a
bug. Blabber all the excuses you want, you cant dress up sschit as it still
smells like scchit.

 

[news.microsoft.com]

2003 .net UPGRADE does NOT have VSS 6.0d

Why o why do they not make a patch available for upgraders. Stupid stupid
stupid.

So, 6.0c is the latest on the upgrade and if you check the microsoft site,
its also the latest there.

 

[ozbear]

Then you should upgrade to version 6.0d.

2003 .net UPGRADE does NOT have VSS 6.0d

Why o why do they not make a patch available for upgraders. Stupid stupid
stupid.

So, 6.0c is the latest on the upgrade and if you check the microsoft site,
its also the latest there.

 

[Piotr Olech]

Sun, 2 Nov 2003 22:37:05 +0100, on
microsoft.public.dotnet.general,microsoft.public.dotnet.languages.csharp,m
icrosoft.public.vsnet.ide,microsoft.public.vsnet.vss, news.microsoft.com
wrote:

[...]

I installed the VSNET IDE and then later i installed the VSS 6.0c and
while I have it configured correctly the right click context menu on the
source explorer does not show source control options, anyideas`? I do not
intend to reinstall the IDE as its bloat and takes ages.

[...]

Hi
I've done the same way (first i've had IDE installed, than later i've
installed VSS). Everything works OK. (I have 6.0c version of VSS).
What I can remember, that until i've added existing soruces to VSS manually
(VSS admin), there were no VSS commands available in context menu.
Do you have a submenu "Source Control" active in "File" menu in your IDE?
Have you created VSS database and added existing files to it?
It should really work.
And you don't need 6.0d version ;-)

Greetz
Piotr Olech

 

[David Goldstein]

Had the same problem... I went through a cycle of uninstalling and
reinstalling VSS 6.0c, invoking REGSVR32 on related DLLs, and doing a
"repair" of VS.NET and along the way it worked so that the Source
Control menu item showed up on the file menu.

I had assumed my problem was because we had installed ClearCase, never
got it working, and then tried to uninstall and it failed miserably.

(ClearCase appears to be the most horrible product ever made, unless you
have a highly paid admin who knows how to make it work - kind of like
Oracle I guess)

Cheers!
-d