Adding file to project does not work

[vrapp]

In VB6, I have a project with the files already in Vault.

I add another existing file to the project. I see a dialog suggesting to add the file to Vault.

If I click the button "advanced", I see the following:

-------------
source code control results
completed

precommanddialog deserializing: the data at the root level is invalid. Line 1 position 1
precommanddialog serializing: exception of type System.argumentnullexception was thrown
Parameter name: graph
------------

I close "advanced" and click "OK" to go ahead with adding the file; the dialog gets closed, but there are no messages in it, and the file is not added to Vault, hotugh in VB project it now appears as under source control.

I'd like to draw attention to the fact that not only it fails to add the file, but, even more importantly, it does not say that it has failed.



[/img]

[lbauer]

What version of Vault are you using?

Is this reproducible? Does it happen whenever you add files to an existing project, or is it happening just for this particular project?

What kind of project is it and what type of file are you adding?

Is there anything in the Vault server log that corresponds to the error?

[vrapp]

>What version of Vault are you using?

3.1.8 (7771)

> Is this reproducible? Does it happen whenever you add files to an existing project, or is it happening just for this particular project?

with this particular project only; however, I was able to fix it by now. The project was actually a project group consisting of two projects, and I was opening the group; when I opened just the project, Vault worked correctly, and after that the group also worked correctly when reopened.

> What kind of project is it and what type of file are you adding?
VB6, file was .DSR

> Is there anything in the Vault server log that corresponds to the error?

nothing in the event log; is there another place to look?


By the way, just noticed that Vault Client shows the following in the Messages upon startup:

Version Check: An error occurred when trying to retrieve version.xml file from the SourceGear website

[lbauer]

nothing in the event log; is there another place to look?

The Vault Server log is sgvault.log and is in the %windir%\temp\sgvault directory on the Vault Server machine.

Version Check: An error occurred when trying to retrieve version.xml file from the SourceGear website

This means the client wasn't able to connect to our server for Vault version information. It's a benign error. You can turn off the version check in the Vault GUI Client under Tools->Options-General->Check for latest Vault version at startup.

[vrapp]

> The Vault Server log is sgvault.log and is in the %windir%\temp\sgvault directory on the Vault Server machine.

nothing interesting there - series of login/logout. It looks like the error occured in the client.

If it happens again, I can collect some information in case you are interested to pin down this problem - if so, please tell me what to collect.

[lbauer]

If you encounter a persistent client-side problem, then client side logging may provide useful information. Use the instructions for VB 6.

http://support.sourcegear.com/viewtopic.php?t=1534

[vrapp]

I had the same issue again; this time, I already opened not the group but regular VB6 project; one of the files in the project was new, recently created; I tried to add it to Vault, and it did not work. The log file is attached.

By the way, producing the log file was problematic as well. When vb6.exe.config was in Vault client directory, as the article instructs, it did not work. It produced the file only after I copied vb6.exe.config to C:\Program Files\SourceGear\Vault Client\VS2003_Client and to C:\Program Files\Microsoft Visual Studio\VB98 .

----------------

update: found the reason, again the file I tried to add was not in the project directory, but in VB6 directory C:\Program Files\Microsoft Visual Studio\VB98, where VB6 is trying to save all new items by default. Still I think Vault might have said something to this effect, rather than showing the new file as eligible for adding, and then showing empty progress box without any status messages in it, and not returning any error.

[lbauer]

You're right, it would be better to have some sort of alert here, although we may be limited in how much we can do within the VB 6 IDE. Microsoft controls most of what happens in MSSCCI integration, which is used by VB.

That's why we have implemented the Enhanced Client integration Vault 4.X, for VS 2005 and 2008. Unfortunately, there's not much we can do to further enhance integration with Visual Basic 6.

We do recommend that all items within a solution are organized so that they are under the solution root, rather than scattered about the local drive.

It wasn't clear from your post whether or not the problem has been resolved. Let us know if we need to troubleshoot this further.

[vrapp]

> It wasn't clear from your post whether or not the problem has been resolved

yes, once I moved the file to the right place, everything worked.

[lbauer]

Thanks.