Reference to CoreLib from EF context?

mije · October 2020

So after auto update to LinqPad 6.10.13 (x64), I can't use it properly to query for EF:
Reference to CoreLib

Data from about box:

Host runtime version: 3.1.8
Default query runtime version: 3.1.8
Default query reference assembly version: 3.1.0
Roslyn Version: 3.7.0-6.20375.2
FSharp.Compiler.Service version: 22.0.3.0
NuGet client version: 5.6.0.5

I am sure it was working just fine with 6.9.

mije · October 2020

And if I add that expected lib:
Added CoreLib

ends up with:
Restore problem

EricJohannsen · October 2020

Similar issue for LinqPad 5 since this morning

JoeAlbahari · October 2020

mije - you definitely want to remove the reference to System.Private.CoreLib - that will only make things worse. Can you post a screenshot of the connection dialog? Also, after removing the reference to System.Private.CoreLib, could you please right-click the connection and choose Show Assembly Resolution Log and post the output?

EricJohannsen - nothing's changed recently in LINQPad 5. Have you tried a restart/reboot?

mije · October 2020

Here is the scree-shot to the local SQL server:
Connection dialog

And also advanced connection options:

Assembly resolution

And the compressed references.html file attached.

JoeAlbahari · October 2020

Can you try refreshing the connection? (Right-click, Refresh)

mije · October 2020

I did that. Even restarted computer. Still the same.
It only happens in SQL queries - both LINQ-to-SQL and EF.
Normal snippet works:

var dt = DateTime.UtcNow;
dt.Dump();

JoeAlbahari · October 2020

Are you able to reproduce this error on another machine?

JoeAlbahari · October 2020

Could you also please run this query and post the result:
http://share.linqpad.net/7xi4sh.linq

mije · October 2020

So, I tried another machine and can't repro there. Hmm, so it's something local to my default work box.
Attached is the result from the snippet.

JoeAlbahari · October 2020

This is a scenario I never anticipated: you have .NET 3.0 Desktop runtime installed without .NET 3.0 Core. To fix this, either uninstall .NET Desktop 3.0, or, if you need it, re-install the 3.0 SDK.

LINQPad normally ignores 3.0 if 3.1 is installed; however with data contexts, it compiles against the earlier version so that you can target queries against either runtime.

I'll update LINQPad in the next build to ensure that this condition triggers a rejection of the 3.0 runtime rather than binding to the runtime assemblies and causing an error.

mije · October 2020

Thanks Joe. I've uninstalled .NET3.0 Desktop. Now everything is working again. Thanks again so much.

Reference to CoreLib from EF context?

Comments