How to install Vault Client in Windows XP 64bit edition

Jaeyoun Yi · Post by **Jaeyoun Yi** » Thu Oct 21, 2004 3:24 am

I've just installed MS Windows XP 64 bit edition on my AMD opteron machine.
And the Whidbey version of Visual Studio (2005) was successfully installed with Microsoft .NET framework 2.0 beta (AMD64).

Then, unfortunately, it is not possible to install vault client !
When I double-clicked the MSI file,
it says "It requires .NET framework 1.1" and it exits.

Moreover, I couldn't find the proper version of .net framework 1.1 for XP 64.
(I tried to install the .NET framework accompanying to Visual Studio 2003, but failed.)

Let me know if I can install the vault client on .NET framework 2.0 beta.
Otherwise, let me know where I can get the .NET framework 1.1 which is installable on my opteron.

Expecting your propmt reply,

Best regards,
Jaeyoun Yi, Ph.D.

dan · Post by **dan** » Thu Oct 21, 2004 7:25 am

We don't recommend running Vault with the .Net Framework 2.0 beta - we have not been able to fully test it, and there are a number of known issues that have not been addressed yet.

After a quick search on the Microsoft site, it looks like the Framework is not available on 64 bit yet. I ran across this blog entry that talks about it "coming soon":
http://blogs.msdn.com/frankred/archive/ ... 36744.aspx

You'll need to contact MS to find out when the framework will be available for 64 bit systems.

Jaeyoun Yi · Post by **Jaeyoun Yi** » Thu Oct 21, 2004 7:08 pm

Thank you for your reply, Dan.

Do you mean that we can use vault client with .net framework 2.0 beta,
in spite of some unknown issues?

If so, I'd like to use it although it's buggy now.
But my current problem is that I can't install it.

Please let me know how to install it on .net framework 2.0 beta.

dan · Post by **dan** » Fri Oct 22, 2004 7:55 am

You can try to use Vault with the 2.0 framework, but it is strickly at your own risk. We do know that IDE integration doesn't work at all, but the Vault client might be usuable.

If this is the client only, you could get around the 1.1 framework requirement by installing the client on a machine that has the 1.1 framework, and then copying the install files over to your machine, which may work. The default location is c:\program files\sourcegear\Vault Client. It should create any registry entries it needs.

Jaeyoun Yi · Post by **Jaeyoun Yi** » Sat Oct 23, 2004 7:50 am

Thank you, Dan.

It sounds very sad that IDE integration won't work at all.
However, using vault client will reduce my tedious jobs, absolutely.

I will try it.

Best regards,
Jaeyoun Yi.

Jaeyoun Yi · Post by **Jaeyoun Yi** » Mon Oct 25, 2004 6:27 pm

I tried as you told me, Dan.
But it doesn't work at all..

When I double-clicked the VaultGUIClient.exe, then it says
"This application has failed to start because the application configuration is incorrect. Reinstalling the application may fix the problem."
and it exits.

Now, I almost give up. I'd better wait till MS releases new .net framework or SourceGear releases a update working on .net framework 2.0

Best regards,
Jaeyoun Yi, Ph.D.

Jaeyoun Yi · Post by **Jaeyoun Yi** » Wed Oct 27, 2004 1:10 am

Dear all,

Now I've succeeded to set up Vault Client 2.0.6 on the AMD64 Windows XP.
I feel I have to inform you of this.

To run on AMD64,
all Vault Client files EXCEPT the "VaultGUIClient.exe.manifest" should be copied from the other Win32 machine to a specific folder.

Then, we now see the Vault client GUI screen on XP-AMD64 (.NET framework 2.0 beta),
although it's somewhat slow.

The first problem I faced is that it's not possible to set working folder on client GUI.
But fortunately, the command-line version of vault.exe is working.
After setting the working folder in the command prompt,
the client GUI is working quite well, up to now.

Best regards,
Jaeyoun Yi.

dan · Post by **dan** » Wed Oct 27, 2004 7:24 am

Thanks for reporting back Jaeyoun. I'm glad you are up and running...