Linqpad 6 - EfCore driver not working
Options
Hi,
first of all congrats for the V6 release - its awesome.
I want to report a bug with the ef core driver in V6.
I have tested it against a 2.2 Version of EFCore and a 3.0-Preview version. Both versions are not working when using the DBContextOptions constructor:

Linqpad 6 correctly recognizes the ctor, but it does not work (Neither when clicking "Test", nor when clicking "OK")
first of all congrats for the V6 release - its awesome.
I want to report a bug with the ef core driver in V6.
I have tested it against a 2.2 Version of EFCore and a 3.0-Preview version. Both versions are not working when using the DBContextOptions constructor:

Linqpad 6 correctly recognizes the ctor, but it does not work (Neither when clicking "Test", nor when clicking "OK")
Comments
-
There seems to be a bug where it can't pick up protected constructors. For now, you can work around it by making your constructor public.
-
Hmm, there must be another issue because my constructor is aready public:
-
This could be tricky to diagnose. Could you first try running the following build:
https://www.linqpad.net/GetFile.aspx?experimental+LINQPad6-Beta.zip
and let me know if it makes any difference? -
I get the same error using the build from your link.
-
Do you get the same error with the parameterless constructor or the one that accepts a string? Click the "Help me decide" link for an example on how to set these up.
-
I've just uploaded a new build here which will log more details of the problem:
https://www.linqpad.net/GetFile.aspx?experimental+LINQPad6-Beta.zip
After it fails, go to %localappdata%\linqpad\logs.linqpad6 and send me the most recent entries in log.txt
Thanks
-
I have successfully tested it with your latest build, no issues any more - thanks!
-
Terrific. I'll push out the new beta.
-
Thanks.
Fyi: I just tried the updater (help => check for update) and I got the following error dialog when updating to the latest version:
However, the update seems to have worked.
-
It looks like I need to ship both X86 and X64 versions of the update patcher.
It will work in spite of the error because it can run the update directly from %localappdata%. It's just failing to patch the original executable, which will cause a slight startup delay.