Visual Studio / Vault 2.03 file access and missing reference

ggaudet · Post by **ggaudet** » Tue Jun 22, 2004 2:31 am

We are using VS 2003 along with Vault 2.0.3 in a trial right now and are experiencing a number of issues when we try to build our solutions. We have several solutions each with several projects.

We get quite a few build errors such as:

-The type or namespace name 'xxxx' could not be found (are you missing a using directive or an assembly reference?)

- The file 'xxx.pdb' cannot be copied to the run directory. The process cannot access the file because it is being used by another process.

Fixing this usually means doing multiple rebuilds, and in some cases closing the solution and starting it up again. There does not seem to be a steady pattern to this however. As well, we did not experience this in VSS.

Any help appreciated.

Gavin.

ggaudet · Post by **ggaudet** » Tue Jun 22, 2004 2:34 am

also, another typical build error is:

- Could not copy temporary files to the output directory.

ggaudet · Post by **ggaudet** » Tue Jun 22, 2004 4:26 am

also, another typical build error is:

- Could not copy temporary files to the output directory.

Post by **jclausius** » Tue Jun 22, 2004 6:16 am

ggaudet:

- Are you using the Vault / VS.Net IDE client? the Vault GUI client?

- How did you add the files to Vault?

- Can you list the directories / files you have placed within Vault? Or more specifically, do you have the bin/Debug or bin/Release directories controlled by Vault?

ggaudet · Post by **ggaudet** » Tue Jun 22, 2004 6:31 am

The answer to you questions:

We are typically doing a 'get latest' with the Vault GUI, and then using the integration with VS.NET.

We got the files into Vault by getting latest in VSS, stripping out the .vss files, and then loading via the Vault GUI into Vault. We realize that we lost our 'history' doing this, but we had some problems importing from VSS.

Not many bin directories, only a couple that I can see, where we have put in testing files (xml). But none of the binaries are being stored in Vault (and we didn't do this in VSS either).

Does this info help? Would deleting the repository and then allowing VS.NET to add solutions/projects to Vault help??

Gavin.

jclausius wrote:ggaudet:

- Are you using the Vault / VS.Net IDE client? the Vault GUI client?

- How did you add the files to Vault?

- Can you list the directories / files you have placed within Vault? Or more specifically, do you have the bin/Debug or bin/Release directories controlled by Vault?

Post by **jclausius** » Tue Jun 22, 2004 7:31 am

Typically, if you are going to use the IDE client, you need to let VS.Net add things to Vault.

Then, try:

1) Unbind everything that is currently bound.
2) Shutdown VS.Net.
3) Provide a new "clean" folder structure for the project's destination from within the Vault GUI client. Also, you may want to "unset" any currently configured working folders.
4) Follow the info provided here http://support.sourcegear.com/viewtopic.php?t=776

Post by **jclausius** » Tue Jun 22, 2004 7:44 am

I submitted before I was finished. Sorry about that.

5) Once everything has been added, shutdown VS.Net.
6) Move, rename, or delete the path where you added the solution.
7) Restart VS.Net, and choose File-> Open Project From Source Code Control from the menu. Retrieve the files for your project in a *NEW* location. It is important to do this step for two reasons:
a) It will retrieve the files with *ONLY* the files required for your project (not the SourceSafe specific files)
b) It will set the read-only status on only the files which require that status for VS.Net to function correctly with the Vault IDE client.

ggaudet · Post by **ggaudet** » Tue Jun 22, 2004 7:47 am

Does that imply that importing from VSS does not work if you intend to use the VS.NET IDE integration?

Gavin.

ggaudet · Post by **ggaudet** » Tue Jun 22, 2004 8:09 am

Hi,

Does Vault 'monitor' the working directory, and temporaily lock any files?

For example, our bin directories are not in Vault, but when we build a solution, VS.NET complains about binaries being locked (as we have dependencies amongst projects within our solutions).

This seems to be our biggest issue, this temporary locking. Sometimes if we rebuild something 2,3,4 times, the locking stops, and things go OK.

We are sure that this did not happen with VSS.

Thanks again for any help.

Gavin.

Post by **jclausius** » Tue Jun 22, 2004 8:13 am

ggaudet wrote:Does that imply that importing from VSS does not work if you intend to use the VS.NET IDE integration?

No. Importing data from VSS is irrelevant here, since the files imported into Vault would not normally contain the files used by VS.Net which contain VSS specific data. These files (MSSCCPRJ.SCC and .VSS files) are normally in your working folder, but not within the repository itself. (I did a terrible job explaining this. If anything is unclear, please let me know.)

However, if you are using a project that was previously bound to VSS, there are extra files on you local disk that are specific to VS.Net / VSS integration. The data contained within these files would cause VS.Net / Vault integration to work incorrectly.

The steps I outlined in previous posts were an indirect way of "cleaning" these files.

Post by **jclausius** » Tue Jun 22, 2004 8:26 am

ggaudet wrote:Does Vault 'monitor' the working directory

Yes. However, I believe this is limited to the Vault GUI client, and only where working folders have been set.

ggaudet wrote:... and temporaily lock any files?

If Vault is not in the middle of a get command, then no.

ggaudet wrote: For example, our bin directories are not in Vault, but when we build a solution, VS.NET complains about binaries being locked (as we have dependencies amongst projects within our solutions).

This seems to be our biggest issue, this temporary locking. Sometimes if we rebuild something 2,3,4 times, the locking stops, and things go OK.

We are sure that this did not happen with VSS.

Thanks again for any help.

Gavin.

Is this a web app? If so, I've seen things like :
- aspnet_wp.exe not releasing the project - Killing aspnet_wp.exe from the task bar usually causes the problem to go away.
- Internet Explorer is working offline.
- All projects in the solution build to the same /bin directory.

Here are some other references that may help:

- http://support.microsoft.com/default.as ... -us;311491

- * http://groups.google.com/groups?hl=en&l ... kmsftngp03

- * http://groups.google.com/groups?hl=en&l ... 26rnum%3D2

* = Google Groups Search - http://groups.google.com/groups?q=canno ... gle+Search

Post by **jclausius** » Tue Jun 22, 2004 8:47 am

jclausius wrote:Yes. However, I believe this is limited to the Vault GUI client, and only where working folders have been set.

Correction on my post - This behavior is in every client (IDE, Command Line, and GUI) where working folders have been set to a corresponding Vault Folder.