LINQPad 5 AnyCPU error - BadImageFormatException on IBM.Data.DB2.dll about linq2db.linqpad HOT 18 CLOSED

That would be great if possible.
Do you know if x64 IBM.Data.*.dll and if yes where can we get them?

from linq2db.linqpad.

You know, I am not using DB2 at all.
Exception I get thrown when I want to connect to MS SQL Server.

But I googled a link
http://www-01.ibm.com/support/docview.wss?rs=4020&uid=swg27016878

Hope this helps.

I can see that client libraries used in linq2db is outdated (version 9.7 used, but current is 11.1).
I think core lin2db project should be updated to support both x86 and x64 versions.

As for me, I am not sure should linq2db support DB2 at all.

from linq2db.linqpad.

Thanks a lot!

from linq2db.linqpad.

I just came across this issue. My suggestion is to allow the linqpad driver to function when provider dlls are missing so that the ones we can delete the ones we dont need.

from linq2db.linqpad.

Any update on this please?

from linq2db.linqpad.

In next versions we'll switch off loading x86 providers in 64 bit environment.
For now I can only suggest not using Any CPU build :(

from linq2db.linqpad.

okay, sounds good. Any idea when the next version will be out?

from linq2db.linqpad.

Unfortunately, the fix that you did Igor is not really working (see screenshot below). The problem still exists with the change in the screenshot because the check is done in the runtime, while the BadImageFormatException happens during the assembly loading and binding. Unfortunately, the only real fix for LINQPad AnyCPU on 64 bit OS is to remove all references to the offending assemblies (DB2, Informix and Oracle Native).

I did it and it works after rebuild. Just in case you want to incorporate the changes Igor, I'm also attaching the diff file.

linq2db.patch.zip

from linq2db.linqpad.

Unfortunately we need more clever solution with dynamic assembly loading.

from linq2db.linqpad.

a try catch around does not help?

from linq2db.linqpad.

Project has references, so libraries will be loaded automatically. And proposed solution just removes a lot of providers that do not support x64 mode.

from linq2db.linqpad.

Are the Librarys only referenced or are they also used?

from linq2db.linqpad.

The libraries are referenced and hence are automatically loaded by .NET Fusion (assembly loading code).

There is no clever solution unfortunately unless you want to resort to dynamic assembly loading and wrapping their types. The alternative is rather to produce 2 builds of plugin for x86 and x64 platforms with preprocessor conditions removing the offending pieces of code.

from linq2db.linqpad.

It is not too hard to load assemblies dynamically. But i have not time do do that right now.

from linq2db.linqpad.

It's not hard, but you'd need to re-wrap every single class from them in your custom loader. It's just going to be a pain in the neck.

The other alternative could be to host the main plugin entry point in the new dll which would hook up to the AppDomain.CurrentDomain.AssemblyResolve event and would suppress the exception on 64 bit OS. It would then need to hide those specific providers from the UI as well.

from linq2db.linqpad.

Also, for anyone else looking for the plugin which would work on 64 bit OS - here's the build that works for me.
linq2db.LINQPad.zip

from linq2db.linqpad.

Working on version that loads data providers dynamically, expect this after 2.0 release.

from linq2db.linqpad.

Fixed in #11

from linq2db.linqpad.