Re: Major bug in VS 2008 source code control

Hello David,

I want VSS back!!!

VSS had a nice feature in that it would compare the actual file and if
it was different, would pull it down again.

AFAIR, when mis-configured VSS would also behave in the manor described

It would also ask first if it should be merged and would act as though
you checked it out the last time you did a get latest.

Again dependant on the settings.

Which sourceControl system are you using? TFS?

If so, I'm afraid I don't have that or know much about it. However there is likely a setting somewhere describing this situation.

I still say at a minimum if I do a get latest and it doesn't give me
the latest version of the file, that's a bug in the functionality.
Because I said "give me the most recent version of this file" and it
tells me "you have it."

Dependant on settings the local file may well be viewed as Latest. If file comparison is done on the basis of file dates for example then your local edits are more recent than what is in source control.

It's actually the safest option. The worst you are going to do is to not get latest and then check in your local file. This at least results in both sets of changes being in the Source Control's history of that file.

If it were to overwrite your local data then you would have lost that. So, by default at least, it may be trying to help.

--
Rory


.

Loading