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?
17  2381 
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" <di********@discussion.microsoft.com> wrote in message
news:OO*************@tk2msftngp13.phx.gbl... 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?
So, this is a bug fix for vs.net? or a new addition?
"Larry R." <lr************@earthlink.net> wrote in message
news:rW****************@newsread4.news.pas.earthli nk.net... 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" <di********@discussion.microsoft.com> wrote in
message news:OO*************@tk2msftngp13.phx.gbl... 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?
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
"Larry R." <lr************@earthlink.net> wrote in message
news:rW****************@newsread4.news.pas.earthli nk.net... 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" <di********@discussion.microsoft.com> wrote in
message news:OO*************@tk2msftngp13.phx.gbl... 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?
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" <di********@discussion.microsoft.com> wrote in message
news:ug**************@TK2MSFTNGP10.phx.gbl... 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
"Larry R." <lr************@earthlink.net> wrote in message
news:rW****************@newsread4.news.pas.earthli nk.net... 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" <di********@discussion.microsoft.com> wrote in
message news:OO*************@tk2msftngp13.phx.gbl... 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?
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system ( http://www.grisoft.com).
Version: 6.0.535 / Virus Database: 330 - Release Date: 1/11/2003
Well, im on 2003 and its 6.0c and MS web site says 6.0c is the latest.
"Jason Wilden" <ja*********@hotmail.com> wrote in message
news:e2*************@TK2MSFTNGP11.phx.gbl... 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" <di********@discussion.microsoft.com> wrote in
message news:ug**************@TK2MSFTNGP10.phx.gbl... 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
"Larry R." <lr************@earthlink.net> wrote in message
news:rW****************@newsread4.news.pas.earthli nk.net... 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" <di********@discussion.microsoft.com> wrote in
message news:OO*************@tk2msftngp13.phx.gbl...
> 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?
>
>
>
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.535 / Virus Database: 330 - Release Date: 1/11/2003
On Mon, 3 Nov 2003 17:03:29 +0100, "news.microsoft.com"
<di********@discussion.microsoft.com> wrote: 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
Its what I have and its not on the web download and I dont have MSDN.
Its a bug, deal with it.
"ozbear" <oz*****@yahoo.com> wrote in message
news:3fa76a96.795101484@news-server... On Mon, 3 Nov 2003 17:03:29 +0100, "news.microsoft.com"
<di********@discussion.microsoft.com> wrote:
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
On Tue, 4 Nov 2003 10:33:54 +0100, "news.microsoft.com"
<di********@discussion.microsoft.com> wrote: 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.
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
"ozbear" <oz*****@yahoo.com> wrote in message
news:3fa96bab.130329343@news-server... On Tue, 4 Nov 2003 10:33:54 +0100, "news.microsoft.com"
<di********@discussion.microsoft.com> wrote:
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.
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 G. Brown" <l@l.l> wrote in message
news:uZ***************@TK2MSFTNGP10.phx.gbl... 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
"ozbear" <oz*****@yahoo.com> wrote in message
news:3fa96bab.130329343@news-server... On Tue, 4 Nov 2003 10:33:54 +0100, "news.microsoft.com"
<di********@discussion.microsoft.com> wrote:
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.
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" <di********@discussion.microsoft.com> wrote in message
news:ur**************@tk2msftngp13.phx.gbl... 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 G. Brown" <l@l.l> wrote in message
news:uZ***************@TK2MSFTNGP10.phx.gbl... 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
"ozbear" <oz*****@yahoo.com> wrote in message
news:3fa96bab.130329343@news-server... On Tue, 4 Nov 2003 10:33:54 +0100, "news.microsoft.com"
<di********@discussion.microsoft.com> wrote:
>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.
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.
"Martin Brown" <re**********@jfjfj.kfkfk> wrote in message
news:OG**************@TK2MSFTNGP11.phx.gbl... 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" <di********@discussion.microsoft.com> wrote in
message news:ur**************@tk2msftngp13.phx.gbl... 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 G. Brown" <l@l.l> wrote in message
news:uZ***************@TK2MSFTNGP10.phx.gbl... 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
"ozbear" <oz*****@yahoo.com> wrote in message
news:3fa96bab.130329343@news-server...
> On Tue, 4 Nov 2003 10:33:54 +0100, "news.microsoft.com"
> <di********@discussion.microsoft.com> wrote:
>
> >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.
>
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.
"Martin Brown" <re**********@jfjfj.kfkfk> wrote in message
news:OG**************@TK2MSFTNGP11.phx.gbl... 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" <di********@discussion.microsoft.com> wrote in
message news:ur**************@tk2msftngp13.phx.gbl... 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 G. Brown" <l@l.l> wrote in message
news:uZ***************@TK2MSFTNGP10.phx.gbl... 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
"ozbear" <oz*****@yahoo.com> wrote in message
news:3fa96bab.130329343@news-server...
> On Tue, 4 Nov 2003 10:33:54 +0100, "news.microsoft.com"
> <di********@discussion.microsoft.com> wrote:
>
> >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.
>
Then you should upgrade to version 6.0d.
On Thu, 6 Nov 2003 13:44:13 +0100, "news.microsoft.com"
<di********@discussion.microsoft.com> wrote: 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.
"Martin Brown" <re**********@jfjfj.kfkfk> wrote in message
news:OG**************@TK2MSFTNGP11.phx.gbl... 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" <di********@discussion.microsoft.com> wrote in
message news:ur**************@tk2msftngp13.phx.gbl... > 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 G. Brown" <l@l.l> wrote in message
> news:uZ***************@TK2MSFTNGP10.phx.gbl...
> > 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 inD:\VSS\SETUP.EXE. > For
> > some reason 6.0d is not available on the internet. By the way it isnot > 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
> >
> > "ozbear" <oz*****@yahoo.com> wrote in message
> > news:3fa96bab.130329343@news-server...
> > > On Tue, 4 Nov 2003 10:33:54 +0100, "news.microsoft.com"
> > > <di********@discussion.microsoft.com> wrote:
> > >
> > > >Its what I have and its not on the web download and I dont haveMSDN. > > > >
> > > >Its a bug, deal with it.
> > > >
> > > >
> > > If you feel that it is a bug, upgrade to 6.0d.
> > >
> >
> >
>
>
>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.
My 2003 came with 6.0c. I had to download 6.0d and upgrade.
Sun, 2 Nov 2003 22:37:05 +0100, on
microsoft.public.dotnet.general,microsoft.public.d otnet.languages.csharp,m
icrosoft.public.vsnet.ide,microsoft.public.vsnet.v ss, 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
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
This thread has been closed and replies have been disabled. Please start a new discussion. Similar topics
by: Wayan |
last post by:
Geekcorps Volunteer - Systems Integration
Kenya, East Africa
Geekcorps http://www.geekcorps.org is in search of systems integration
professionals experienced in developing communication systems...
|
by: Stylus Studio |
last post by:
DataDirect XQuery(TM) is the First Embeddable Component for XQuery That
is Modeled after the XQuery API for Java(TM) (XQJ)
BEDFORD, Mass.--Sept. 20, 2005--DataDirect Technologies...
|
by: YellowfinTeam |
last post by:
Yellowfin is proud to announce the release of 3.1.
The major theme of this release is enhanced integration capability. We
have introduced a range of new web services and authentication
processes...
|
by: YellowfinTeam |
last post by:
Marketplace: Yellowfin reporting 3.1 with BIRT Integration
Yellowfin is proud to announce the release of 3.1.
The major theme of this release is enhanced integration capability. We
have...
|
by: YellowFin Announcements |
last post by:
Marketplace: Yellowfin reporting 3.1 with BIRT Integration
Yellowfin is proud to announce the release of 3.1.
The major theme of this release is enhanced integration capability. We
have...
|
by: aa123db |
last post by:
Variable and constants
Use var or let for variables and const fror constants.
Var foo ='bar';
Let foo ='bar';const baz ='bar';
Functions
function $name$ ($parameters$) {
}
...
|
by: ryjfgjl |
last post by:
If we have dozens or hundreds of excel to import into the database, if we use the excel import function provided by database editors such as navicat, it will be extremely tedious and time-consuming...
|
by: emmanuelkatto |
last post by:
Hi All, I am Emmanuel katto from Uganda. I want to ask what challenges you've faced while migrating a website to cloud.
Please let me know.
Thanks!
Emmanuel
|
by: BarryA |
last post by:
What are the essential steps and strategies outlined in the Data Structures and Algorithms (DSA) roadmap for aspiring data scientists? How can individuals effectively utilize this roadmap to progress...
|
by: nemocccc |
last post by:
hello, everyone, I want to develop a software for my android phone for daily needs, any suggestions?
|
by: marktang |
last post by:
ONU (Optical Network Unit) is one of the key components for providing high-speed Internet services. Its primary function is to act as an endpoint device located at the user's premises. However,...
|
by: Hystou |
last post by:
Most computers default to English, but sometimes we require a different language, especially when relocating. Forgot to request a specific language before your computer shipped? No problem! You can...
|
by: Oralloy |
last post by:
Hello folks,
I am unable to find appropriate documentation on the type promotion of bit-fields when using the generalised comparison operator "<=>".
The problem is that using the GNU compilers,...
|
by: jinu1996 |
last post by:
In today's digital age, having a compelling online presence is paramount for businesses aiming to thrive in a competitive landscape. At the heart of this digital strategy lies an intricately woven...
| |
