Dean Harding wrote:
> That's because firebird is a 32-bit DLL, and your .NET application is
> running as a 64-bit process by default. You cannot load 32-bit DLLs into
> 64-bit processes.
>
> There're two solutions. The simplest is to run your .NET app as a 32-bit
> process. This one will work today, and simply requires that you compile your
> application as explicitly Win32, rather than "Any CPU" (by passing the
> /p:Win32 command-line option to msbuild, usually).
>
> The other option is that firebird needs to be released as both 32-bit and
> 64-bit (so that would be two separate DLLs). That's out of scope of the .NET
> provider mailing list, though... hopefully one day, because I'd like to see
> that one, too :)
>
> Note: This only applies to firebird embedded, where the DLL is loaded
> in-process. The server version is different.
Yes, your absolutely right. I've miss that we're talking about embedded. :)
--
Jiri {x2} Cincura
http://blog.vyvojar.cz/jirka/ | http://www.ID3renamer.com
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Firebird-net-provider mailing list
Firebird-net-provider@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
