You may indeed need an assembly reference added, but .NET 4.0 has its own provider installation related issues.
Here are notes that have worked for me with visual studio 2010 using .net 4.0 on a 64 bit Windows 7 and XP. Visual Studio 2010 does NOT support development with .NET 4.5 but use the full .NET 4.0, not the client 4.0 in your project properties. Install: NETProvider-3.0.2.0.msi The client MSI install has a problem with a bug in .NET 4.0. So, you need to replace the dll installed with a .NET4.0 version. Copy both files from NETProvider-3.0.2.0-NET40.7z over the installed ones at "C:\Program Files (x86)\FirebirdClient". For XP, adjust install path "C:\Program Files\FirebirdClient". Then, copy the dll file over top of the GAC copy at "C:\Windows\Microsoft.NET\assembly\GAC_MSIL\FirebirdSql.Data.FirebirdClient\v4.0_3.0.2.0__3750abcc3150b00c". Install: DDEXProvider-3.0.0.0.msi, use advanced option to add visual studio 2010 components. Install DDEXProvider-3.0.0.0-src\reg_files\VS2010\ FirebirdDDEXProvider64.reg to fix msi missing stuff. (For XP, install DDEXProvider-3.0.0.0-src\reg_files\VS2010\FirebirdDDEXProvider32.reg) Components in the toolbox still don't operate as I expected but the dialogs for data sources and entity framework tools seem to work. Be sure to use a database alias to avoid issues with windows pathname characters. Hope that helps, +BillJ ------------------------------------------------------------------------------ See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk _______________________________________________ Firebird-net-provider mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
