Re: Upgrade to SP6 doesn't do anything
- From: "Alin Constantin [MSFT]" <cnila@xxxxxxxxxxxxx>
- Date: Wed, 30 Nov 2005 23:54:52 -0800
Build 9484? You mean 9848, perhaps?
It may be possible that:
- another VSS install was found on the hard drive and SP6 upgraded that one
- you had some VSS application running and SP6 couldn't upgrade some of the
files (especially ssus.dll)
- you had SourceSafe6 installed in a folder different than default and SP6
may not recognize it
Anyway, you can extract the VSS binaries from the SP6 yourself. Here is how
to do it:
- make sure you don't have VSS applications open (and that ssapi.dll is not
in use, if you have controlled FrontPage projects on the machine)
- run the Vs6sp6.exe and let it unpack in a folder of your choice.
- open that folder in Windows Explorer and navigate into VS6sp64.cab by
double clicking it.
- sort the files by the Path column, and scroll to the bottom, looking for
all the files in VSS\Win32
- multi-select those 23 files (analyze.exe - ssus.dll), right click, choose
Extract, and then pick your SourceSafe_Install_dir\Win32 folder.
--
Alin Constantin
This posting is provided "AS IS" with no warranties, and confers no rights.
"Arne" <Arne@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:C729F1A9-7561-431E-9B0A-454D041800B9@xxxxxxxxxxxxxxxx
>I installed service pack 6, but why am i still on build 9484?
>
> This is what microsoft says should happen, but it doesn't:
> This service pack upgrades all previous installations of Visual SourceSafe
> 6.0 to 6.0d (Build 31222), fixing known issues such as automation
> incompatibilities in 6.0d (Build 9848)
> http://msdn.microsoft.com/vstudio/previous/ssafe/default.aspx
>
.
- Prev by Date: Re: VSS 2005 == 6.0 with a new logo
- Next by Date: Re: Visual Source safe 6.0d corrupt
- Previous by thread: Re: VSS 2005 == 6.0 with a new logo
- Next by thread: Re: Visual Source safe 6.0d corrupt
- Index(es):
Relevant Pages
|
