Where to register CLSID entry for Visual Studio 2017 or later version

Archana Soni 1

Hi,
For one of our project, we had created some registry entry under HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID<registry entry> and some under specific VS version. This seems to be working fine with VS 2015 or prior releases. From VS 2017 on-wards we have moved VS specific entries in *.pkgdef file. But we are not exactly sure about registry entries for CLSID. If we make under HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\ it does work with VS 2017 but our doubt is on system where multiple instance of VS 2017 exist will it work ? Or we need to move these inside *.pkgdef file ?

Archana Soni 1 Reputation point

2022-01-25T13:08:02.507+00:00

Can someone look into our query and suggest here ?

1 answer

Anna Xiu-MSFT 25,801 Reputation points Microsoft Vendor

2021-12-17T10:03:36.56+00:00

Hi @Archana Soni ,

Welcome to Microsoft Q&A!

Do you want to detect the instances of Visual Studio 2017?

Changing registry entry of Visual Studio is not recommended. You can use Tools for detecting and managing Visual Studio instances.

In addition, the details of existing Visual Studio instances are located in C:\ProgramData\Microsoft\VisualStudio\Packages_Instances. You can also check it.

Sincerely,
Anna
*
If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Please sign in to rate this answer.
Archana Soni 1 Reputation point

2021-12-20T13:18:34.1+00:00

Thanks for the reply, I don't want to change the registry for VS. But want to create our custom registry entry under classes\CLSID. In case of multiple instance , Wanted to get clarity that if we update HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\<Custom entry> will it work for all the instance of VS 2017 ? If not then how to define CLSID entry in *.pkgdef file ?

Archana Soni 1 Reputation point

2021-12-21T13:28:30.823+00:00

it's quite urgent for us as our Customer is waiting to get solution. Can Someone help here ?

Anna Xiu-MSFT 25,801 Reputation points Microsoft Vendor

2021-12-22T03:26:41.987+00:00

I’m now trying to involve someone more experienced in this topic to research this issue. It may take some time, please be patient to wait. Any update I will share here. Thanks for your understanding.

Archana Soni 1 Reputation point

2022-01-04T11:29:53.303+00:00

Hi @Anna Xiu-MSFT ,
Happy New Year..
Did you get some one to look into. It's quite urgent for us as Customers are waiting to hear back..

Thanks very much for the help..

Anna Xiu-MSFT 25,801 Reputation points Microsoft Vendor

2022-01-05T09:18:09.137+00:00

Sorry for my late reply. We did not find a suitable solution because modifying the registry is not a recommended behavior. What is the reason you want to associate VS with CLSID entry? What does this CLSID key do for your project? We would like to investigate it further in order to find the workaround that meets your requirements.

Archana Soni 1 Reputation point

2022-01-10T13:15:52.117+00:00

Somehow I missed your comment. We have registry based DDEX provider for DB2 Databases. To support Database project so far we were adding CLSID entry of some feature of Database project. Till VS 2015 we were making all entries in registries, But from VS 2017 we have private *.pkgdef file to achieve the same. If adding in registry is not recommended then how to make entry in *.pkgdef file ?

Archana Soni 1 Reputation point

2022-01-18T09:37:11.647+00:00

Hey @Anna Xiu-MSFT , any progress on this. it's been 1 month now. And Our Customer is pushing us for a solution...
Sign in to comment