How to deploy VSTO AddIn in Terminal Server environment with roaming profiles?

Peter Eberlein 1 Reputation point
2020-12-28T09:00:25.857+00:00

According to kb 2571899 (https://learn.microsoft.com/en-us/troubleshoot/dotnet/framework/clickonce-not-support-roaming-profiles) ClickOnce cannot be used for roaming profiles. Does this also affect VSTO-AddIns, which are not deployed by MSI?

Only some users (member of a defined usergroup), which have logged in a terminal server should get an VSTO-AddIn. Thats why I think .msi cannot be used. How to solve this problem?

Windows
Windows
A family of Microsoft operating systems that run across personal computers, tablets, laptops, phones, internet of things devices, self-contained mixed reality headsets, large collaboration screens, and other devices.
4,732 questions
Office Development
Office Development
Office: A suite of Microsoft productivity software that supports common business tasks, including word processing, email, presentations, and data management and analysis.Development: The process of researching, productizing, and refining new or existing technologies.
3,473 questions
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Mark Heitbrink 96 Reputation points
    2020-12-28T10:03:01.61+00:00

    You can´t. Addins are Office/machine specific not users specific. Redirect them to a different RDS. Or install it for all and disable it by Registry per user.

    change LoadBehavior:
    https://learn.microsoft.com/en-us/visualstudio/vsto/registry-entries-for-vsto-add-ins?view=vs-2019

    0 comments
  2. Peter Eberlein 1 Reputation point
    2020-12-28T11:10:26.133+00:00

    Of course VSTO-AddIns can be user specific. And in my case they must, because every user can have his own settings for the AddIn, which are until now stored in %localappdata%\apps\2.0\data....\user.config.