Best Of

Thanks - this should now be sorted out. This is hopefully the tail end of the DLL hell I've had to deal for LINQPad 9

@Joe thanks. I am not sure how LinqPad5 is working. The whitelisting is a black box to me. I think that what is working is that CB is actually pretty dumb. I find that mostly it blocks exes but I can replace dlls and it seems OK with that. Sometimes.

@alirezanet said:
Is there any update on the Linux version? linqpad is the only reason I am stuck with windows on my work machine

Taking into account this comment and the time macOS version development took (~3 years), I think that Linux version won't be available at least in 2-3 years.

There's a few gremlins in there - they should be fixed for the next build. (Note that after the fix, the exact workaround you have won't work - you would need to use HtmlElement.StyleAttribute instead of HtmlElement["style"].)

Funny warning:

Was testing something in a Windows Sandbox and noticed this as well.

It is correctly shown as installed on my main install and it seemed to be the exact same version of Dotnet 8 as well. So I went hunting to see if I could figure it out for myself and found this.

Looks like a cut-and-paste error, and so it only shows DotNet Version 8 as installed if Dotnet Version 6 is also installed (which it is on my main install)

Thanks - will fix.

Another Idea and solution I use when working with JavaScript libraries in LINQPad is to embed html and templatize the data.

Here is an example that should apply to any js library.

http://share.linqpad.net/3q6lra.linq

I don't believe this is relevant.

I can assure you that this would be a ton of work to do properly, even without the UI LINQPad doesn't use MSBuild or project files, relies on numerous host services and and there are many features that would require special-casing.