Hi friends;

Here is the case where I want to install or sign or register ( or whatever you call) a .vsto file. This file installs when double clicked on it with the help of VSTOinstaller.exe but it says the location is not added in trusted location. I tried adding this location manually to trusted location but it doesnt work . There is some signing of certificates involved ( Please refer : http://blogs.msdn.com/rextang/). But that too doesnt work. Has anybody encountered with these types of files? I want to install this file silently.

Thanks;
1 Comment   [ + ] Show Comment

Comments

  • you mean to say that we need to capture that part using wise or install shield ?
Please log in to comment

Community Chosen Answer

1
From memory, VSTO is Visual Studio Tools for Office, right? So you've built a "solution" in Office, right? What does the solution comprise? Some DLLs, presumably a template for the target Office app? Maybe some registry junk?

Doesn't VS have a deployment tool which can create MSIs? Use that: it's better than nothing.

Failing that, I'd simply capture it into an MSI. Try the AppDeploy Repackager if you don't have a proper authoring tool like Wise or InstallShield.
Answered 09/03/2009 by: VBScab
Red Belt

Please log in to comment
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
thats right vsto means visual studio tool for office. I installed a source given to me which adds "SPS.VSTO" file. Its file for office Excel. When I launch shortcut a message box pops up which asks me to install SPS.VSTO ( it uses VSTOINSTALLER.exe). On clicking install it adds one registry key in HKCU\Software\Microsoft\VSTO\Security\Inclusion\{Random Key}\ (some values)

Now this random key changes everytime I install SPS.VSTO even if I install it on same machine again and again.

So I thought it wont be good to capture this registry and add it in my pacakge as registry key changes everytime ( Is this really harmful?). So I went for method for silent installation as prescribed in my previous post. But thats not working.

What do you mean by "deployment tool which can create MSIs?"
Answered 09/03/2009 by: nkhawale
Senior Yellow Belt

Please log in to comment
0
So I thought it wont be good to capture this registry and add it in my pacakge as registry key changes everytime That registry entry is created by the VSTO installer. If you don't use it, it won't be created!What do you mean by "deployment tool which can create MSIs?"In VS, there's what used to be called the 'Setup and Deployment Wizard'. I can't recall what the latest flavour calls it but, whatever it is, can you not create an MSI using it?

As previously, if not, just capture its installation. You should probably remove the VSTO installer junk from the registry in the final package.
Answered 09/03/2009 by: VBScab
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity