File missing after fresh branch & open from vault

[rja]

A developer in our staff recently added a new DLL to a "dependencies" solution folder in our solution.

He then merged his branch into our trunk. All is well.

Now, whenever we branch from trunk, and open that solution in Visual studio, that DLL is missing.

We then have to open vault client, and explicitly "get latest" on that DLL. The missing status then goes away and all is well again.

First, why is this happening and how do we prevent it in the future?

Second, what can we do to fix the present issue.


Thanks for the help

[lbauer]

What version of Vault are you using? What version of Visual Studio? Are you using Enhanced or Classic integration for Visual Studio?

Where is that .dll in relation to the solution/project file? Is it under the solution/project in the tree, or in a different directory?

[rja]

SourceGear Vault Standard Version 5.1.2

Visual Studio 2010 Version 10.0.4x

Enhanced Integration

The DLL in in a solution folder named Dependencies in the root of the solution.

[lbauer]

Is there a "missing" icon on the .dll when you open the solution, or does the .dll file not appear at all?

[rja]

Sorry it's been a few days.

For reference, we have this issue with 2 .cs files, as well as 3 dlls.

here are my steps to reproduce.

1. Branch from trunk & commit (done in vault client)
2. Open visual studio 2010
3. Open from vault
4. Select newly created branch
5. Attempt to build solution.
6. Get missing reference errors for same files that have been giving us issues.
7. Get latest from solution explorer in visual studio. Show hidden files in affected project.
8. Has no effect, file still missing. Not just hidden, but simply doesn't get downloaded
9. Open vault client
10. Go to newly created branch, ensure file is in branch.
11. Get latest on that branch from vault client
12. Go back to visual studio, click yes when prompted to reload projects
13. File is there but hidden
14. Right click, include in project. Has "added" icon.
15. Commit the add.
16. Next person that branches repeats this process.

This is the long version obviously. At this point, we get latest form vault client, know to show hidden files, add it in and the solution builds.

I suspect that at some point, that maybe these files / dlls were committed while they were hidden / excluded, and that they aren't getting "added" when committed since they already exist in the branch.

If I was debugging this, I'd probably start by adding some files to a solution, somehow get them to be hidden. Commit them. Branch, and get latest from VS 2010.

My guess is the bug is in the visual studio integration code, at least as far as "getting" that file, since getting latest from vault client seems to work.

Finally, I bet if we removed the file completely from the main branch, and checked in fresh versions, that this would no longer be an issue.

//Edit:

The DLLs DO have missing icons next to them in solution explorer.

Screenshot below shows the missing DLLs after a fresh branch is made, and get latest from visual studio 2010.

Screenshot of missing files

Screenshot.png (9 KiB) Viewed 5691 times

[lbauer]

I'd suggest we schedule a remote assist session where I can take a closer look. Email me at support at sourcegear.com, ATTN: Linda.

Please include a link to this forum post.