Commented by: danielrail (danielrail)

I tried by simply changing the registry keys from 14_Config to 15_Config, but that simply created a 15_Config registry key that only contained the registry keys for Firebird, and nothing else. It looks like that they have changed how the integration works.

Here's the reference of the breaking changes with regards to the registry:
https://docs.microsoft.com/en-ca/visualstudio/extensibility/breaking-changes-2017

Commented by: André Ziegler (andre.ziegler)

@danielrail

yes, but this could be fixed by implementing it as VSIX (DNET659).

In "public override void Register(RegistrationContext context)" here you can set all values that are in reg.

Commented by: André Ziegler (andre.ziegler)

@danielrail

Here is some background on the issue:

3rd party database tools such as MySQL requiring some work to integrate with Visual Studio 2017
http://www.visualstudioextensibility.com/2017/03/19/3rd-party-database-tools-such-as-mysql-requiring-some-work-to-integrate-with-visual-studio-2017/

In this case, since Visual Studio 2017 uses its own private Registry hive, the setup has some work to do using the RegLoadAppKey

https://msdn.microsoft.com/en-us/library/windows/desktop/ms724886(v=vs.85).aspx

Commented by: @cincuranet

Here's a manual, for now, tutorial how to do it: https://www.tabsoverspaces.com/233604-installing-ddex-provider-for-firebird-into-visual-studio-2017/ .

Commented by: @cincuranet

DNET659