When installing add-ins for Visual Studio, a number of different paths can be used. One of them is
C:\Documents and Settings\All Users\Application Data\Microsoft\MSEnvSharedAddins – in a default installation of a US English Windows. Obviously a proper installer would use
Environment.GetFolderPath(Environment.SpecialFolder.CommonApplicationData) to make sure the path is correct for the current system and for the current language. For example, for a German system the result would be
C:\Dokumente und Einstellungen\Alle Benutzer\Anwendungsdaten\Microsoft\MSEnvSharedAddins.
Now, the funny thing is that a part of the path is stored by Visual Studio verbatim. To be precise, VS stores the path as
%ALLUSERSPROFILE%\Application Data\Microsoft\MSEnvSharedAddins, as you can see in VS using Tools/Options/Add-in/Macros Security.
Obviously they forgot that the
Application Data part wouldn’t be called that in a localized version of Windows. So if you want to install your add-in into that path, you should make sure you fiddle around with it to create a mixed-language version, which fits the template used in the VS settings.
Sorry, this blog does not support comments. Why not?
I used various blog hosting services since this blog was established in 2005, but unfortunately they turned out to be unreliable in the long term and comment threads were lost in unavoidable transitions. At this time I don't want to enable third-party services for comments since it has become obvious in recent years that these providers invariably monetize information about their visitors and users.
Please use the links in the page footer to get in touch with me. I'm available for conversations on Keybase, Matrix, Mastodon or Twitter, as well as via email.