Hi,
At March 8, 2017, 3:09 PM, Jiří Činčura wrote:
>> Also, what is the timeline to support VS 2017? 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
> Also, what is the timeline to support VS 2017? 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
Known mistake. Your machine config entry and GAC does not match.
--
Mgr. Jiří Činčura
https://www.tabsoverspaces.com/
On Wed, Mar 8, 2017, at 18:28, Paul Dryden wrote:
> Hi,
>
> I was able to get Firebird to show up in the provider list by copying an
> setting to my app.config file. I found
Hi,
At March 8, 2017, 2:16 AM, Jiří Činčura wrote:
> Check whether the registry entries are there (for VS2015).
That was the problem. I did double-click on the .reg file and Windows
told me that the entries were added, but they were not. I just used
the Import function inside RegEdit, and
Support Visual Studio 2017
--
Key: DNET-739
URL: http://tracker.firebirdsql.org/browse/DNET-739
Project: .NET Data provider
Issue Type: Improvement
Components: DDEX Provider
Affects Versions: 5.8.0.0
