System.Data.SQLite

The very same null exception with very same call stack happens.

I would have commented to the original ticket but I'm not allowed to.

This appears to have a different underlying cause than [ad28d8e026c4c227],
which was addressed by check-in [6b6fb5374d] on trunk and subsequently merged
into the 1.0.112 release branch.

Initial analysis has been frustrated by the inability to get visibility into
the assembly loading process when running on .NET Core (3.0).

When using the dedicated test program (testef6), the System.Data.SQLite.EF6
assembly cannot be loaded for reasons that are yet unclear.  It produces a
generic error message and very few details.  However, when loading the same
assembly via Eagle (for .NET Core), everything appears to work fine.

This leads me to think there is a configuration file issue with the (multiple)
JSON files used to configure the .NET Core assembly loading mechanism.

If you have any additional details which may be useful,
please add them to this ticket.

Further testing and analysis appears to reveal that the System.Data.SQLite.EF6
assembly included with the 1.0.112.1 does work.

Research is ongoing.

I am unable to reproduce the issue.

In the attached PNG, I see a warning for the System.Data.SQLite.Linq package;
however, since that package is not supported when using .NET Standard, I'm not
sure what the underlying issue is.  The image itself cuts off the warning in
the dependencies window.

I'll try to create a minimalistic sample from scratch.

Is the .linq file of any use to you, or do you need a zip with .cs+.csproj?

Sorry, I don't really use LINQPad.

The zip file should be more useful, I hope.

Thanks, I'll look further into this...

This turned out to be a NuGet packaging problem.  The issue will be resolved in
the NuGet packages versioned "1.0.112.2".

Thanks for the help.

Looks good now :)

I wonder that I neither have to reference `System.Data.SQLite` nor `System.Data.Linq` packages for the sample to work -- is this correct=intended?