Vault with VS 2005 ?

Jaeyoun Yi · Post by **Jaeyoun Yi** » Tue Jan 25, 2005 2:40 am

We are now using vault 2.0.6 and VS 2003.
But we are planning to change our development environment to VS 2005 for a specific reason.

For some days, I've tested vault 2.0.6 and VS 2005 Beta2.
Fortunately the vault component works well with VS 2005 IDE.

But, the most severe problem is around Vault GUI Client.
Whenever VS 2005 IDE runs, the vault gui client doesn't show the contents properly.
Folder trees are properly displaying, but most of files are not displaying.
And if some files are checked-in in the VS 2005 IDE, then vault GUI client shows the infinite pop-up error messages, which says some errors occured around the state file.
But if VS 2005 IDE exits and launches the vault client again, then no problem.

Since I heard that you wouldn't support 2.x any more,
I just want to check if the new version 3.x also has this problem or not, before deciding to purchase the so-called 'gold-support'...

Best regards,
Jaeyoun Yi, Ph.D.

Jaeyoun Yi · Post by **Jaeyoun Yi** » Tue Jan 25, 2005 2:48 am

I tried to connect your demo server.
But the server can't add a new user, so I failed.

dan · Post by **dan** » Tue Jan 25, 2005 9:36 am

We plan to be fully compatible with the 2.0 framework (and VS 2005) with Vault 3.1, which should be out in the next few months.

In the meantime, you can always try running the GUI client using the 1.1 framework.

To do that, edit or create the app.config file in the same folder that the GUI client runs. It should contain something like:

<?xml version="1.0" encoding="utf-8" ?>
<configuration>
<startup>
<requiredRuntime version="v1.1.4322" safemode="true"
</startup>
</configuration>

Look in C:\WINDOWS\Microsoft.NET\Framework for the specific version of the framework you have installed.

Also, the demo user problem should be sorted out now, so you should be able to add yourself as a new demo user.

Jaeyoun Yi · Post by **Jaeyoun Yi** » Tue Jan 25, 2005 11:49 am

Thank you, dan.
I'll try your recommendation soon. (Now, I'm outside the office.)

How about the .NET integrated components?
Do you have any similar method to force the .net-integrated component to run on a specific version?

Jaeyoun Yi · Post by **Jaeyoun Yi** » Tue Jan 25, 2005 12:01 pm

Sorry for frequent post.. ^^;

In the vault folder, there are two .config files

vault.exe.config and VaultGUIClient.exe.config

Which one shall I edit?
Or, need I create new one, "app.config"?

dan · Post by **dan** » Tue Jan 25, 2005 2:02 pm

Hmmm. Good question, and I'm not actually sure, although I would bet someone on this list would.

I would say try putting the <startup> element in the VaultGUIClient.exe.config and see if it works, otherwise create a new app.config file in the same folder. It might be that app.config works on any .net app, whereas specific executables only work on specifically named .config files?

Post by **jclausius** » Tue Jan 25, 2005 2:19 pm

vault.exe.config applies to the Command line client, and VaultGuiClient.exe.config applies to the GUI client.

cpdaniel · Post by **cpdaniel** » Tue Jan 25, 2005 5:49 pm

Dan - app.config is automatically re-named by Visual Studio to yourapp.exe.config - that's the name that the CLR actually looks for. At runtime app.config will be summarily ignored.

Jaeyoun Yi · Post by **Jaeyoun Yi** » Wed Jan 26, 2005 2:11 am

Thank you all guys...

In conclusion, it was successful for me.
Vault 2.0.6 is now working with VS2005 on my desktop !!!

But, contrary to your comment,
the VaultGUIClient.exe must run with dot-net framework 2.0.

After adding the following three lines to VaultGUIClient.exe.config file,
it works very well with VS2005.

<startup>
<supportedRuntime version="v2.0.41115" />
</startup>

Without the above lines in the config file,
when VS2005 checked-in some files in a folder,
VaultGUIClient shows a infinite pop-up error messages if I clicked the folder in which the checked-in files reside.
Or, sometimes, it displays empty folder contents without any message.
In this latter case, the error message pops up when I right-clicked the folder in the tree-view.

For your information, the error message was;

"The working folder state information for (working-path) is incompatible with this version of Vault. Please choose a different working folder path. The specific compatibiity exception was:
Ticks should be between DateTime.MinValue and DateTime.MaxValue.
Parameter Name: ticks"

The last message was in Korean.

Anyway, by modifying the config file to force the VaultGUIClient.exe running on framework 2.0,
it works.. (I've tested some other basic features, too, including check-in/check-out/history/get-latest/...)

Thank you very much for your comment.

Best regards,
Jaeyoun Yi. Ph.D.