Ddex Provider Firebird Install

admin
Ddex Provider Firebird Install Rating: 8,5/10 1351 votes

Installing the Firebird.Net Data Provider into Visual Studio I just spent a frustrating few hours trying to install the Firebird.Net Data Provider into Visual Studio. Installing the data access components itself is not terribly difficult but installing the GUI designer (DDEX) is another matter altogether.

I have been stuck for a number of days now with this problem. I see a lot of people have this problem and I have tried many things but am still unsuccessful. Please can someone help me. I am running Windows 7 64bit, MS Visual Studio 2010, Firebird DDEX 2.0.5 and NetProvider 2.7.0.0.

I have closely followed stackoverflow question in conjunction with the ReadMe file supplied with DDEX and other articles online in trying to install everything. I have done the following: • Install NetProvider 2.7.0.0 to C: Program Files (x86) FirebirdClient. • Extract DDEX 2.0.5 files to C: Program Files (x86) FirebirdClientt. • Edited the registry file FirebirdDDEXProvider64 in C: Program Files (x86) FirebirdClient reg_files VS2010 so that the 'CodeBase'='%Path% FirebirdSql.VisualStudio.DataTools.dll' now reads 'CodeBase'='C: Program Files (x86) FirebirdClient FirebirdSql.VisualStudio.DataTools.dll' and then I installed it.

Visual Studio 2005/2008/2010/2012/2013/2015 DDEX Provider for Firebird ====================================================================== This project is supported by: ----------------------------- Sean Leyne (Broadview Software) The DDEX Provider for Firebird provides integration of FirebirdClient into Visual Studio. In order to use Firebird Client in Visual Studio, you have to perform these steps. Preinstallation steps. ------------------------- Copy files from this archive to some place (must be accessible for VS).

Install FirebirdClient into the GAC. Zrazok protokolu virobnicho naradi v dnz. Free full version software downloads. --------------------------------------- You can use gacutil utility to do this or to check whether it's correctly installed.

The gacutil show you also the signature for assembly, that will be used later. Modify machine.config file. ------------------------------ Modify it like this (for 64bit systems you have to edit '32bit version' of this file, because Visual Studio is 32bit, but there's no problem with editing the '64bit version' too):. And substitute (these informations you can find using gacutil): -%Version% with the version of the provider assembly that you have in the GAC.

Note: Notice, that in configSections there isn't signature of FirebirdClient but the signature of assembly from framework. Import registry file. ------------------------ There's a couple of *.reg files in installation. There are files for 32bit and for 64bit system, so select appropriate version for your system.

There are also files in 'withSDK' directory. These can be used for Visual Studio with VS SDK installed. The files not in this directory are for systems without Visual Studio SDK (it's *not* the.NET FW SDK!) and it's probably the best choice for a lot of developers.

The selected registry file needs be modified to set the correct paths. To do this, substitute%Path% in the file with path for the DDEX files where you copyied them in step 0 (remember to backslash the backslash character). IMPORTANT: The DDEX provider didn't work with Express editions of Visual Studio. (If you want to build the sources you will need to have C# and C++ installed and VS SDK.).