This article will discuss the installation of DDEX Provider for Microsoft Visual Studio 2017. At this time (08/08/2017) there is still no DDEX Provider installer for Visual Studio 2017. The latest version is, which does not prescribe the required data source (Firebird Data Source) In the Visual Studio 2017 shell. This is due to the fact that Visual Studio 2017 started to use its private registry to store its settings, instead of the configuration file.
Initially, the list of sources looks like this:
VS2017without firebird sourceWhat it is necessary to make, that in the list of sources there was a treasured record “Firebird Data Source”? Detailed instructions below. The whole procedure will take you no more than 5 minutes.

Step 1: Install the DDEX Provider 3.0.2

Download DDEX Provider 3.0.2 and install it. Usually it is installed in the folder C: Program Files (x86) FirebirdDDEX.

Step 2. Preparing the reg-file

Download the 32-bit or 64-bit version of the base reg-file, depending on the bit depth of your operating system. Locate the folder on your computer where the Visual Studio 2017 settings are stored. Typically, it is located here: C: Users AppData Local Microsoft VisualStudio. Find the folder whose name begins with 15.0_. In this case it is 15.0_3ab834cd. Microsoft Visual Studio 2017 Settings path

Open the base reg file in Notepad and make the following changes:

###15.0_Config### to 15.0_3ab834cd (11 replacements)

###DDEX_PATH### to C:Program Files (x86)FirebirdDDEX (1 replacement)

Double-slashes are required. The result is the following file:


The reg-file is ready. Save it.

Step 3. Edit the private registry

Run Regedit. Highlight the HK_USERS section. Select File -> Load Hive. We select the file privateregistry.bin, which is located in the settings folder of Visual Studio 2017 (in this case C: Users AppData Local Microsoft VisualStudio 15.0_3ab834cd). Specify VS2017PrivateRegistry as the name of the bush


Click OK. Run on execution of the previously saved registry file or import it through regedit. Expand the HKEY_USERS section. Highlight the newly created section of VS2017PrivateRegistry. Choose File -> Unload Hive.


Run Visual Studio 2017 and check to see if the Firebird Data Source appears in the list.

Запускаем Visual Studio 2017 и проверяем, появился ли источник Firebird в списке.

11 thoughts on “How to install DDEX Firebird Provider in Microsoft Visual Studio 2017

  1. Omar Aaron says:

    I do not even know how I ended up here, but I believed this post was great. I do not understand who you might be however definitely you’re going to a famous blogger for those who aren’t already. Cheers!|

  2. Great blog here! Also your website loads up very fast! What host are you using? Can I get your affiliate link to your host? I wish my website loaded up as quickly as yours lol|

  3. Thanks on your marvelous posting! I actually enjoyed reading it, you may be a great author.I will always bookmark your blog and will often come back in the future. I want to encourage you to ultimately continue your great work, have a nice morning!|

  4. Hey! I’m at work surfing around your blog from my new apple iphone! Just wanted to say I love reading through your blog and look forward to all your posts! Carry on the excellent work!|

  5. Excellent post. I am facing many of these issues as well..|

  6. Gerardo says:

    Good Afternoon, this process works with Visual Studio 2019??


    1. ost_user says:

      I guess not

  7. Gerardo says:

    Good nigth, unfurtunately this don’t work in Visual Studio 2019
    I can see the type of firebird connection, but when I want to add a new connection the window closes, and if I try to add an entitiy framework, the type of firebird connection is not present.

    I hope you can help me, greetings …

  8. Simone says:

    It work also for visual studio 2019??

  9. ni says:

    I have followed all the steps, and I’m able to select Firebird Data Source option, but when I start setting the connection, the window disappears
    any clue?

  10. Eloir Carli says:

    Working on Visual Studio 2019.

    The samee for me – “window disappears”

    What I did for adjusting to VS2019:
    Editing base reg-file
    – replaced ###15.0_Config### with 16.0_46c7cf6b
    – changed Section Name of Registry to VS2019PrivateRegistry

Leave a Reply

Your email address will not be published. Required fields are marked *