|
|
|
date: 6 Jun 2006 00:01:10 -0700,
group: microsoft.public.vstudio.sourcesafe
back
Re: VSS 2005 - broken labels after migrating
> Unfortunately VSS 6.0c "sucks" as well. I found very peculiar behavior.
This is by design. VSS may keep 2 copies of a file with a same, one deleted
and one not.
> Small secret: Microsoft inside does not use VSS (the same story for MFC
> and similar "cool" technologies, suitable only for 'Hello, world'
> applications). They use some quite powerful source control system that
> does not even has GUI -- ahhh...forgot it's name.
Don't be so sure about that...
SourceSafe 6.0 sources are stored in a VSS database. TeamFoundatioServer
sources are stored in a TFS database.
Other groups use a choice of VSS, TFS or SourceDepot (and possibly other SCM
systems), depending on their needs.
Btw, SourceSafe is a MFC application...
--
Alin Constantin
This posting is provided "AS IS" with no warranties, and confers no rights.
"Michael Pryhodko" wrote in message
news:1149752626.890006.282510@i40g2000cwc.googlegroups.com...
> Hi Alin
>
>> The database format in VSS2005 is not changed from VSS6 so there is no
>> need
>> for this "migration" with archive/restore.
>> You could have simply used VSS2005 on the old database...
>> Since you get "Version not found" messages it is most likely when you
>> used
>> archive/restore you did not archived all versions of the files inside the
>> folder
>
> I used the same archive created in VSS 6.0c:
> - restored it into freshly created VSS 2005 database
> - restored it into freshly created VSS 6.0c database
>
> in first case command-line utility fails to retrieve ~90% of labels
> in second case it retrieved 100% of them without any message.
>
> Maybe database format was not changed. But changed may be in:
> - restore utility
> - command-line utility
> - smth else
>
> and these changes ruins all my versioning control.
>
> About archiving or copying database -- I needed to transfer only one
> project, not whole database.
>
> Unfortunately VSS 6.0c "sucks" as well. I found very peculiar behavior.
> In this case:
> - my_file.cpp is listed in 'Deleted Items' property page of VSS project
> - new my_file.cpp exists in the same VSS project (in my case it was
> shared there from another project)
>
> After archive/restore operation VS2003 goes crazy and refuses to see
> this file on VSS. It marks it with red tick without exclamation, tries
> to checkin it every time (successfully but without any success :-) ).
> The only workaround I found is to purge old my_file.cpp instance. But
> this is destructive operation and normally prohibited. Also it makes
> devastates labeling mechanism -- you can't get by label if it refers to
> purged file.
> Moral of the story -- never use archive/restore, always copy database
> and delete unnecessary stuff.
> Even bigger moral: move to REAL source control system. VSS is extremely
> old and buggy -- it should go to /dev/nul after IIS, SQL6.5 and IE4.0.
> Small secret: Microsoft inside does not use VSS (the same story for MFC
> and similar "cool" technologies, suitable only for 'Hello, world'
> applications). They use some quite powerful source control system that
> does not even has GUI -- ahhh...forgot it's name.
>
> Didn't it sound a little bit frustrated? Maybe because I am frustrated.
> ;-)
>
> Bye.
> Sincerely yours, Michael.
>
date: Fri, 9 Jun 2006 14:16:00 -0700
author: Alin Constantin [MSFT]
Re: VSS 2005 - broken labels after migrating
Hi Alin
> > Unfortunately VSS 6.0c "sucks" as well. I found very peculiar behavior.
>
> This is by design. VSS may keep 2 copies of a file with a same, one deleted
> and one not.
You missed the point. Visual Studio 2003 goes crazy after
archive/restore operation if given folder has one deleted file and one
not deleted file with the same name. Before archive/restore everything
works fine. Maybe it is VS2003 to blame, but why it never happened
before moving sources?
> > Small secret: Microsoft inside does not use VSS (the same story for MFC
> > and similar "cool" technologies, suitable only for 'Hello, world'
> > applications). They use some quite powerful source control system that
> > does not even has GUI -- ahhh...forgot it's name.
>
> Don't be so sure about that...
> SourceSafe 6.0 sources are stored in a VSS database. TeamFoundatioServer
> sources are stored in a TFS database.
> Other groups use a choice of VSS, TFS or SourceDepot (and possibly other SCM
> systems), depending on their needs.
Ok, you got me here, Microsoft is a big company with all sorts of
people and software inside. I've got some friends here, they are quite
happy not to use VSS. And one guy told me that he does not know if
anybody uses VSS inside MS. Well, I guess you can't know everything
even if you work inside.
> Btw, SourceSafe is a MFC application...
So what? I have seen quite a few complex applications written using
MFC. And every time it was a big mistake on the long run. VSS has no
complex GUI and does not have any requirements for performance of GUI
parts -- so MFC fits here quite nicely. Luckily this application was
never extended to the point where MFC becomes unbearable burden. But
this topic is for another newsgroup ;-).
Bye.
Sincerely yours, Michael.
date: 10 Jun 2006 18:33:06 -0700
author: Michael Pryhodko
|
|
