I have a set of files that are duplicated, with minor variations, in different folders. Like this:
/project/foo1/bar1.cs
/project/foo1/bar2.cs
/project/foo1/bar3.cs
/project/foo2/bar1.cs
/project/foo2/bar2.cs
/project/foo2/bar3.cs
All of these files are part of the same VS project.
Occasionally, when opening /project/foo2/bar1.cs, I'll actually be presented with /project/foo1/bar1.cs. Comparing changes with past versions of /project/foo2/bar1.cs, it looks as though Vault is confused by the fact the both files have the same name (bar1.cs) while ignoring their location (foo1 vs. foo2). Compare changes shows me the wrong file. This is all while using VS 2003.
I'm not sure if this is an issue with Vault or VS 2003. I've seen it four or five times over the last six months. Let me tell you, it's pretty scary. Let me know if I can provide additional info.
Thanks,
Matt
trunnell (dot) public (at) cognix (dot) net
Wrong file, same name. Possible data loss?
Moderator: SourceGear
Yes, it would be good to know whether this is VS or Vault. One way to investigate this is to check the Vault status of the file in the Vault GUI client when the wrong file is displayed. Does it think it is the same version as the one on the Vault server? If you do a Get from the Vault GUI client, does it retrieve the right versions of the right files? That might help in determining whether the problem is Vault, VS, or a combination of Vault/VS.