none
Deploying an Outlook Solution (InstallShield/ClickOnce & Windows 8 SmartScreen) RRS feed

  • Question

  • Which of the two - InstallShield or ClickOnce, would you say is the best way to deploy an Outlook solution?

    I take it I am going to have problems on Windows 8 with SmartScreen either way?

    Is it worth getting a certificate?

    Thursday, June 11, 2015 9:48 PM

Answers

  • Hello Darryl,

    It depends. Nobody can't give the definitive answer. The most noticeable thing is that you can't deploy per-machine add-ins by using ClickOnce installers. But if you need to get auto-update feature working - ClickOnce is what you need. You may find both ways described in depth in the Deploying an Office Solution by Using ClickOnce section in MSDN.

    ClickOnce:

    You can update the solution without having to distribute a new setup program to users. This deployment option is simpler, but you can't show users custom setup pages. Also, solutions must be installed multiple times on any computer that has more than one user.

    Windows Installer:

    The setup program can install a solution for all users of a computer at the same time, rather than the current user only. You also have a bit more control over options that appear to users when they install your solution. For example, you can show a licensing agreement or enable users to install specific components of a solution. However, if you update the solution, you must distribute a new setup program.


    P.S. As for the certificates and SmartScreen, before a solution can run on user computers, either you must grant trust or users must respond to a trust prompt when they install the solution. To grant trust to the solution, sign the manifests by using a certificate that identifies a known and trusted publisher. See Trusting the Solution by Signing the Application and Deployment Manifests.

    Thursday, June 11, 2015 9:59 PM

All replies

  • Hello Darryl,

    It depends. Nobody can't give the definitive answer. The most noticeable thing is that you can't deploy per-machine add-ins by using ClickOnce installers. But if you need to get auto-update feature working - ClickOnce is what you need. You may find both ways described in depth in the Deploying an Office Solution by Using ClickOnce section in MSDN.

    ClickOnce:

    You can update the solution without having to distribute a new setup program to users. This deployment option is simpler, but you can't show users custom setup pages. Also, solutions must be installed multiple times on any computer that has more than one user.

    Windows Installer:

    The setup program can install a solution for all users of a computer at the same time, rather than the current user only. You also have a bit more control over options that appear to users when they install your solution. For example, you can show a licensing agreement or enable users to install specific components of a solution. However, if you update the solution, you must distribute a new setup program.


    P.S. As for the certificates and SmartScreen, before a solution can run on user computers, either you must grant trust or users must respond to a trust prompt when they install the solution. To grant trust to the solution, sign the manifests by using a certificate that identifies a known and trusted publisher. See Trusting the Solution by Signing the Application and Deployment Manifests.

    Thursday, June 11, 2015 9:59 PM
  • Just a quick one.

    What kind of issues will I get with Windows 8 SmartScreen. Will it block the install?

    Like this...

    Friday, June 12, 2015 8:55 AM
  • Did you try to sign the manifests with a digital signature?
    Friday, June 12, 2015 9:39 AM
  • Could I use a test certificate for ClickOnce?
    Friday, June 12, 2015 2:59 PM
  • Yes, you can use a temporary certificate for testing. I'd recommend asking ClickOnce specific questions on the ClickOnce and Setup & Deployment Projects forum instead.
    Friday, June 12, 2015 3:18 PM