I have Vault 2.0.3 installed and am working on my laptop and office machine (and other developers). When I attempt to "Get Latest Version" after working on and creating new files on my laptop, my office machine does not retrieve them (sometimes) in VS.NET. I had to open the Vault Client from VS and look for the files that showed "Missing" in the Vault Client (what does that mean?). I then selected those files and chose get latest version (again, from the Vault Client, not VS).
They still did not show up in VS until I "showed all files" and manually included them in the project.
I have had one of my other developers complaining about the same issue where VS .NET (2003) is not getting the latest version or all the new files. Is this a known issue or a fix for it? It is frustrating my development team and they are questioning our move away from SourceSafe.
I checked the forum for any help and I did not find anything (the HTTP Chunked registry fix was already applied and/or checked in the new version).
Thanks for any help.
Vault 2.0.3 Not Getting all Files
Moderator: SourceGear
If the files are not included as part of your VS project, then VS won't fetch them as part of a Get operation. VS only manages files that are part of the project (it doesn't handle other files that happen to be in the same working folder).
Missing means the file exists in the repository, but does not exist in your local working folder, so the files appear to have had the correct state.
Missing means the file exists in the repository, but does not exist in your local working folder, so the files appear to have had the correct state.
-
BrianGorbett
- Posts: 6
- Joined: Thu Apr 01, 2004 9:11 pm
Not getting everything
I am probably not wording this correctly. On my laptop I am creating a new folder in VS and new files in that folder. After I am done, I check everything in.
I get to work and open VS on my work machine and "Get Latest Version", but the new folder I created on my laptop in VS and checked in, does not download or add to my work VS Solution.
We have had similar problems with files not coming down after other developers have added them to the solution.
Thanks.
I get to work and open VS on my work machine and "Get Latest Version", but the new folder I created on my laptop in VS and checked in, does not download or add to my work VS Solution.
We have had similar problems with files not coming down after other developers have added them to the solution.
Thanks.
OK, I tried a few things, and I think I found something that might reproduce this.
If your project file is renegade on your work machine, and you make changes to your project on your laptop (such as adding files to a subfolder), a Get won't overwrite the project file on your work machine unless you explicitly tell it to overwrite. Not overwriting it means it doesn't know about the extra files just added, so it won't get them.
Usually a project file won't just turn Renegade (meaning it was modified but not checked out). However, if you have the file checked out to you on one machine, and then bring up the project on a separate machine, Visual Studio knows that the file is checked out to you, but it doesn't know that it is checked out on another machine, and allows you to make changes to it, even though you can't check it in from that location.
Once the project file is checked in from the laptop, at that point the file can be renegade on the work machine, and the Gets won't work until you do a Get - overwrite.
So, as a working practice, if you are going to modify the project (add files, etc), don't work on two machines while logged in as the same user in Vault. If you do find yourself in this situation, a simple Get from the GUI client should fix things.
Hope this helps,
If your project file is renegade on your work machine, and you make changes to your project on your laptop (such as adding files to a subfolder), a Get won't overwrite the project file on your work machine unless you explicitly tell it to overwrite. Not overwriting it means it doesn't know about the extra files just added, so it won't get them.
Usually a project file won't just turn Renegade (meaning it was modified but not checked out). However, if you have the file checked out to you on one machine, and then bring up the project on a separate machine, Visual Studio knows that the file is checked out to you, but it doesn't know that it is checked out on another machine, and allows you to make changes to it, even though you can't check it in from that location.
Once the project file is checked in from the laptop, at that point the file can be renegade on the work machine, and the Gets won't work until you do a Get - overwrite.
So, as a working practice, if you are going to modify the project (add files, etc), don't work on two machines while logged in as the same user in Vault. If you do find yourself in this situation, a simple Get from the GUI client should fix things.
Hope this helps,