Best Of

Amazing!

I would recommend LINQPad 7 (and LINQPad 5) to my colleagues.

Thanks,

You can also temporarily deactivate the license - it won't use up a transfer if you re-activate the same machine.

Don't think you should be using any LinqPad objects.

Try

imglst.Images.Add("BackColor", System.Drawing.Image.FromFile(Path.Combine(absPath, "ChooseColor.bmp")));

Check out the 7.4.3 beta - the EF Core driver now reads the Category attribute.

The problem is that the assemblies load into both ALCs. I've logged an issue here:
https://github.com/PowerShell/PowerShell/issues/17492

Thank you to the guys at ClearScript - and sorry at the frustration expressed in my message

Thank you very much! I can verify that it's running fine without the workaround. Even works without using the "Copy all NuGet assemblies into a single local folder" setting.

I can only guess that it might be a hangover from a .NET Framework implementation

That's correct, and we need that code to support a number of legacy scenarios. The problem is that it's needlessly throwing an exception in this scenario. In fact, manual loading of the native assembly is completely unnecessary with newer frameworks.

We've posted ClearScript 7.3 which addresses this issue. We've tested it with LINQPad 7 and 5. Fantastic tool, BTW 😊