[JoeAlbahari]

It's changed such that it won't shadow assemblies in the third-party drivers folder.

However, LINQPad has also been changed such that it always looks for assemblies first in the user's data context folder, so it should only load from the drivers folder if the assembly isn't present in the user's folder. (Unless you explicitly load an assembly using Assembly.LoadFrom).

[Jeremy Thomas]

JoeAlbahari, on 23 March 2012 - 05:09 AM, said:

It's changed such that it won't shadow assemblies in the third-party drivers folder.

Why?

Is there any solution to my problem other than rolling up the 3 driver assemblies (AW.LLBLGen.DataContextDriver.dll, AW.Helper.LLBL.dll and AW.Winforms.Helpers.LLBL.dll) into one?
Like maybe LINQPad intercepting the second attempt to load SD.LLBLGen.Pro.ORMSupportClasses.NET20.DLL and returning the already loaded one.

[JoeAlbahari]

I've rewritten the shadowing system in the latest beta. Let me know if it makes any difference.

[Jeremy Thomas]

JoeAlbahari, on 04 April 2012 - 10:59 PM, said:

I've rewritten the shadowing system in the latest beta. Let me know if it makes any difference.

Yes and noIt no longer loads SD.LLBLGen.Pro.ORMSupportClasses.NET20.DLL twice but running a query still fails - i think because the driver seems to be now loaded twice.

Also as usual in the selfservicing variant queries run but with shadowing on there is no sql output

This post has been edited by Jeremy Thomas: 05 April 2012 - 04:15 AM

[JoeAlbahari]

Do you know the two locations from where it's being loaded? Does it let you run the following?

AppDomain.CurrentDomain.GetAssemblies().Dump();

[Cyber World Uk Ltd]

On a related matter when shadow assemblies is turned on GetSchema is called withAppDomain.CurrentDomain.BaseDirectory set to the linqpad directory rather than the directory of the custom assembly like it is when shadow assemblies is off, and this is causing a problem for me.

Shouldn't the BaseDirectory always be the custom assembly directory either way?

[tightline]

Cyber World Uk Ltd, on 03 August 2012 - 05:41 AM, said:

On a related matter when shadow assemblies is turned on GetSchema is called withAppDomain.CurrentDomain.BaseDirectory set to the linqpad directory rather than the directory of the custom assembly like it is when shadow assemblies is off, and this is causing a problem for me.

Shouldn't the BaseDirectory always be the custom assembly directory either way?

Thanks!