New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support Visual Studio 2017 [DNET739] #681
Comments
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: |
Commented by: André Ziegler (andre.ziegler) 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) Here is some background on the issue: 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/ . |
Modified by: @cincuranet |
Commented by: @cincuranet |
Submitted by: André Ziegler (andre.ziegler)
Is replaced by DNET659
Votes: 2
Can you please add support for the Visual Studio 2017 to the DDEX Installer? Currently it only supports Vs versions up to VS2015.
The text was updated successfully, but these errors were encountered: