microsoft end user runtime web installer

To avoid these conditions, don't change the solution's Assembly Name value after you deploy the solution.

If the VSTO Add-in was installed before the assembly name was changed, the end user will never receive updates.

If the end user installs both versions, the application will load both VSTO Add-ins.

If you deploy two manifest files, the following conditions might occur: If you change the Assembly Name value in the Application page of the Project Designer after you've already deployed a solution, the publishing tools will modify the Setup package to have one Setup.exe file and two deployment manifests.

Change the assembly name causes conflicts For more information, see Event logging for Office solutions. You can use these messages from the event logger to resolve installation and deployment problems. You can use the event viewer in Windows to see error messages that are captured by the Visual Studio Tools for Office runtime when you install or uninstall Office solutions.

Troubleshoot Office solutions by using the event viewer See Features available by Office application and project type.

The information in this article applies to document-level projects and Visual Studio Tools for Office (VSTO) Add-in projects. This article introduces how to solve common problems that you might encounter when you deploy Office solutions.

Microsoft end user runtime web installer