none
Deploying Excel Add-in RRS feed

  • Question

  • I recently created an Excel Add-in that uses a custom ribbon in the home bar with a few buttons.

    The addin works fine on my computer and the ribbon is always docked in the home bar even after opening and closing excel. However, after publishing my add-in and having someone else install it on their computer, the add-in ribbon disappears after closing excel. They have the add-in enabled and it is checked in the customize ribbon options under the home tab. What is the proper way to deploy the add-in so all users will have the ribbon even after closing excel??? 

    • Moved by Amanda Zhu Tuesday, August 5, 2014 7:22 AM better forum
    Monday, August 4, 2014 9:52 PM

Answers

  • This link is very useful and can learn you the proper way how to create a Windows Installer file (.msi) for your Office add-in by using VS and deploy it.

    You may also see this link to deploy your add-in for All Users.
    Monday, August 4, 2014 11:56 PM
  • Hello,

    There are two main reasons why end users don't see the custom Ribbon UI of your add-in.

    1. Something is wrong with your markup. When an add-in generates the Ribbon XML markup with errors Office applications hides the custom UI silently.

    To display error messages for the Fluent UI

    1. Click the Microsoft Office Button, and then click Application Options to display the dialog box.

    2. Click Advanced, and then find the General section of the options.

    3. Select Show add-in user interface errors.

    But the add-in continues running anyway.

    2. Microsoft Office applications can disable add-ins that behave unexpectedly. If an application does not load your add-in, the application might have hard disabled or soft disabled your add-in.

    Hard disabling can occur when an add-in causes the application to close unexpectedly. It might also occur on your development computer if you stop the debugger while the Startup event handler in your add-in is executing.

    Soft disabling can occur when an add-in produces an error that does not cause the application to unexpectedly close. For example, an application might soft disable an add-in if it throws an unhandled exception while the Startup event handler is executing.

    When you re-enable a soft-disabled add-in, the application immediately attempts to load the add-in. If the problem that initially caused the application to soft disable the add-in has not been fixed, the application will soft disable the add-in again.

    You can read more about this in the How to: Re-enable an Add-in That Has Been Disabled article in MSDN.

    Finally, the Deploying an Office Solution section in MSDN provides the following articles that describe the required steps for creating installers in depth:

    Deploying an Office Solution by Using Windows Installer

    Deploying an Office Solution by Using ClickOnce

    Tuesday, August 5, 2014 10:00 AM

All replies

  • This link is very useful and can learn you the proper way how to create a Windows Installer file (.msi) for your Office add-in by using VS and deploy it.

    You may also see this link to deploy your add-in for All Users.
    Monday, August 4, 2014 11:56 PM
  • Hello,

    There are two main reasons why end users don't see the custom Ribbon UI of your add-in.

    1. Something is wrong with your markup. When an add-in generates the Ribbon XML markup with errors Office applications hides the custom UI silently.

    To display error messages for the Fluent UI

    1. Click the Microsoft Office Button, and then click Application Options to display the dialog box.

    2. Click Advanced, and then find the General section of the options.

    3. Select Show add-in user interface errors.

    But the add-in continues running anyway.

    2. Microsoft Office applications can disable add-ins that behave unexpectedly. If an application does not load your add-in, the application might have hard disabled or soft disabled your add-in.

    Hard disabling can occur when an add-in causes the application to close unexpectedly. It might also occur on your development computer if you stop the debugger while the Startup event handler in your add-in is executing.

    Soft disabling can occur when an add-in produces an error that does not cause the application to unexpectedly close. For example, an application might soft disable an add-in if it throws an unhandled exception while the Startup event handler is executing.

    When you re-enable a soft-disabled add-in, the application immediately attempts to load the add-in. If the problem that initially caused the application to soft disable the add-in has not been fixed, the application will soft disable the add-in again.

    You can read more about this in the How to: Re-enable an Add-in That Has Been Disabled article in MSDN.

    Finally, the Deploying an Office Solution section in MSDN provides the following articles that describe the required steps for creating installers in depth:

    Deploying an Office Solution by Using Windows Installer

    Deploying an Office Solution by Using ClickOnce

    Tuesday, August 5, 2014 10:00 AM