How do I manage my private gallery in 2017 version using the registry like it did in vs 2015?

How to manage a private gallery using registry settings https://msdn.microsoft.com/en-us/library/hh266735.aspx?f=255&MSPPError=-2147217396

The article above details how I do it in 2015 by modifying the registry, but the problem is that VS no longer stores this information in the registry (I don't think so). It used to be in the ExtensionManager folder in 2015 versions ([HKEY_CURRENT_USER \ Software \ Microsoft \ VisualStudio \ 12.0 \ ExtensionManager \ Repositories ...), but this folder no longer exists (along with 30 others that are missing).

Presumably VS stores them in a private registry:

https://docs.microsoft.com/en-us/visualstudio/extensibility/breaking-changes-2017#visual-studio-registry

I don't understand if I can use the registry the same way I used to, and if not, what is the recommendation for the easiest way to do it ... we basically use the registry to install our private VS in developers just by clicking the .reg file. so they don't have to install this themselves ... actually the same as in this answer: Programmatically specify the Private Extension Gallery in Visual Studio 2012

I would rather not create food for the atom, but if this is the last resort, then I am all ears.

thank

+3
visual-studio vsix


source to share


No one has answered this question yet

See similar questions:

3
Specify private extension gallery programmatically in Visual Studio 2012

or similar:

91
Packages not loading after installing visual studio 2015 RTM
22
Where does Visual Studio 2017 store its configuration?
2
Visual Studio 2015 Cannot Connect to Team Foundation Server 2017: TF31002
2
How to create a Visual Studio Extension (VSIX) targeting Visual Studio 2010-2017
1
Publishing the Visual Studio 2017 Multi-Draft VSIX to Market
0
Toolbox Control Installer (TCI) in Visual Studio 2017
0
Personal internal galleries error "Failed to connect to server [...]"
0
Where are the theme settings for Visual Studio 2017?
0
VSIX Extension - Change DLL Path
0
Running a VSIX Compatible Project for VS 2015 and VS 2017



All Articles
Loading...
X
Show
Funny
Dev
Pics