Losing References contained in Solution

[tmpava]

We are running Vault Version 5.0.4 and
We're running a Visual Studio 2008 (Version 9.0.30729.4462 QFE) VB Web Solution under Framework 3.5, (SP1) which has several Application References (dll's) (shown via Property Page). The solution is checked into Vault, but when a 2nd person does a 'get latest' on the Web solution, the application references no longer appear. Can anyone shed a light on what may be happening?

The exculsion files are:
File Exclusions:
*.clw; *.dca; *.dll; *.dsw; *.exe; *.hlp; *.incr; *.ncb; *.opt; *.pdb; *.plg; *.scc; *.suo; *.user; *.vbw; *.vspscc; *.vssscc; *.webuser

Folder Exclusions: bin; debug; obj; release

We do not have this issue with any of our other solutions and the exclusion files are the same. Can anyone shed any light on why this is happening?

Thank you

[lbauer]

The file exclusions wouldn't have an impact on this.

It could be a configuration issue with the project in source control or with the 2nd user's machine.

Try this: Set a new working folder on your machine and Get a fresh copy of the project. Do you have all the references?

[tmpava]

Tried what you suggested and the application references did not pull in. Thoughts, Suggestions?

[lbauer]

Are these third-party references, rather than the built-in Microsoft references?

If so, the reason the second person is not seeing the references is that they are not in source control. So when the second person opens the solution, Visual Studio can't find the referenced DLLs because they are on your computer, not his.

To make this work, and delete your references from the project, then move the DLLs into the project directory in your working folder. Then re-add the references. Next check in your changes and also add the DLLs to the repository using the Vault GUI client. You can use detect files to add, and mark the checkbox next to the DLLs in order to add them (since by default they are excluded).

Then the next person opening the solution would GET the project from the Vault GUI client. This would also get the DLLs to their working directory. Now when the other user opens the solution, Visual Studio will have all the files it needs, including the references.