I have a quite large ASP.NET project stored in Vault (about 400 files). When I am trying to open it ("Open from Source Control"), I get a message saying that the project is actually under souce control but cannot be opened for some reason. As a result, folder structure of the project created on the client but no files are downloaded from Vault.
Notes:
1. This happens only to large web projects. Smaller web projects open fine.
2. This happenes both when I am trying to open the project on the same where Vault Server is installed and any computer on the network. So this seem to be not a network issue.
This is very frustrating, please help. I am currently evaluating Vault to see if we can use it in our work.
BTW -- adding such a project into Vault from VS.NET is also a non-trivial task. It takes about an hour, and 80% is spent only on creating project's folder structure in the database. Filling the folders with files is MUCH faster.
Thanks,
Alex Avrutin
AW/Systems
Fail to open a large web project from Vault in VS 2003
Moderator: SourceGear
Are you invoking Open From Source Control each time you enter Visual Studio? Note that this command should only be invoked once, in order to set up the project in a new working folder. Invoking it to a folder that already exists that has SCC bindings will cause errors. After you have invoked Open from Source Control, you simply need to open the project for it to connect to Vault.
-
Alex Avrutin
How did you put the project files into Vault? It doesn't look like Visual Studio thinks the files are controlled from Vault.
If this was a project that was controlled in VSS, the general steps are:
1. Unbind from VSS
2. Switch to Vault as SCC provider
2.5. Possibly copy files to a different working folder.
3. Add solution to Vault from IDE from local machine.
4. On local machine, start using the project (no need to do an Open From Source control)
5. On other machines, do an Open From Source Control one time only.
If this was a project that was controlled in VSS, the general steps are:
1. Unbind from VSS
2. Switch to Vault as SCC provider
2.5. Possibly copy files to a different working folder.
3. Add solution to Vault from IDE from local machine.
4. On local machine, start using the project (no need to do an Open From Source control)
5. On other machines, do an Open From Source Control one time only.
-
Guest
If you can access the Vault server with the Vault standalone GUI client, then the domain controller wouldn't be the issue.
When you added the solution to source control, did it add it to Vault? Check the GUI client and verify that the files you think should be there are in fact there.
Since you are in a testing phase, I would recommend trying the add again, perhaps even from a different machine, to try to see where the problem might be. The VS error message is coming from VS, not from Vault, so it isn't clear what problem VS thinks there is.
When you added the solution to source control, did it add it to Vault? Check the GUI client and verify that the files you think should be there are in fact there.
Since you are in a testing phase, I would recommend trying the add again, perhaps even from a different machine, to try to see where the problem might be. The VS error message is coming from VS, not from Vault, so it isn't clear what problem VS thinks there is.
-
Alex Avrutin