Issue Details (XML | Word | Printable)

Key: DNET-739
Type: Improvement Improvement
Status: Closed Closed
Resolution: Won't Fix
Priority: Major Major
Assignee: Jiri Cincura
Reporter: André Ziegler
Votes: 2
Watchers: 1

If you were logged in you would be able to see more operations.
.NET Data provider

Support Visual Studio 2017

Created: 08/Mar/17 08:03 AM   Updated: 05/Oct/18 02:15 PM
Component/s: DDEX Provider
Affects Version/s:
Fix Version/s: None

Environment: Win10 + VS2017
Issue Links:

 Description  « Hide
Can you please add support for the Visual Studio 2017 to the DDEX Installer? Currently it only supports Vs versions up to VS2015.

 All   Comments   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
danielrail added a comment - 08/Mar/17 02:52 PM
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:

André Ziegler added a comment - 09/Mar/17 07:26 AM

yes, but this could be fixed by implementing it as VSIX (DNET-659).

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

André Ziegler added a comment - 24/Mar/17 08:03 PM

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

Jiri Cincura added a comment - 25/Mar/17 07:10 AM

Jiri Cincura added a comment - 05/Oct/18 02:15 PM