Linqpad6 loads same assembly twice, leading to type1 != type1 issues

Trying to migrate driver to linqpad6 and have issue with same assembly loaded twice, which leads to errors with reflection code. See attached screen.
Same System.Data.Common.dll loaded twice (same name, version, path) with second load right after dirver assembly.

We don't load this assembly explicitly and I don't even have time to intercept load - it is already loaded second time in driver class static constructor.

Any ideas/suggestions what's going on and how to fix it?


Sign In or Register to comment.