Running installation from command line

Apr 17, 2012 at 7:31 PM

Hi there!

We would like to install the Word 2007 Redaction Tool on all our client workstations (Windows 7/Office 2010) using a command line in a batch job.  Is that possible?  If so, what would the command syntax be? 

Thanks very much.

C.

Coordinator
Apr 18, 2012 at 6:59 PM

The add-in is a standard VSTO 2010 project, so I believe it should be possible, though you'd likely need to compile the project to set it up.

I haven't done it, but what should work is:

 

Apr 19, 2012 at 1:35 PM

Thanks tristand.  I must admit to being in a bit over my head here, but I'll follow your instructions and see what I can do.

Thanks again!

C.

Apr 20, 2012 at 7:14 PM

Okay, I've followed the instructions at http://msdn.microsoft.com/en-us/library/bb772078.aspx to run the vstoinstaller.exe.  Running it interactively is fine.  Since the publisher can't be verified, a prompt is displayed warning us of this and gives us the option to "Install" or "Don't Install".  Clicking on "Install" installs it perfectly.  However, we want to deploy this to 100+ workstations by running it from a command line and so, we need to run it in silent mode.  I tried doing just that, but because the publisher can't be verified, the default action for the prompt (which is what silent mode will take) is "Don't Install", so it does not get installed in silent mode.  If I run it from the command line without silent mode, the prompt is displayed and I can then click on "Install" to install it.

You mentioned grabbing the MSI file, which is what our tech folks really want, but I can't find one in the downloaded source code -- just the VSTO file.  Is there any way to get or make an MSI file for this?

Thanks again.

C.

 

Coordinator
Apr 22, 2012 at 5:37 AM

Setup isn't my area of expertise, but I believe that because it's a VSTO solution, you'll ultimately need to use VSTOInstaller to get the solution set up on the machines correctly.

What I think you'll need to do is recompile the source code for yourselves using Visual Studio to sign the project with a certificate that's trusted by the PCs in your organization, and then deploy that version using the method in the MSDN article. I'm not aware of any other way to get around the requirement around the signature in an unattended install. 

Apr 23, 2012 at 1:23 PM

That's kind of what I thought.  I was hoping to avoid the whole certificate thing, but I guess that's just the way it is now.  Thanks for all your help, tristand.  Much appreciated.

 

C.