Best Of
Re: LINQPad.Controls.Image.Style is overwritten when a LINQPad.Util.ScaleMode is active
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"]
.)
Re: Request: Add options to temporarily override result limit? (per query and per dump)
Funny warning:
Re: .Net 8.0.0 Installed and working but shown as Not Installed in .NET dropdown
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)
Re: Dump Plotly.Net
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.
Re: Ability to compile .linq into exe
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.
Re: LINQ to DB Oracle connection successful but population fails
This looks like an issue with the LINQ to DB driver. You can report it here:
https://github.com/linq2db/linq2db.LINQPad/issues
Re: LINQ to DB Oracle connection successful but population fails
Filled issue https://github.com/linq2db/linq2db.LINQPad/issues/72, but it will help if you provide some details there:
- oracle version
- result of
SELECT USER FROM DUAL
query (no need to provide real user name, just information wether it is null, empty or some value)
LinqPad5 OData CS0234 The type or namespace name 'User' does not exist in the namespace 'LINQPad'
Hi fellow LinqPad lovers,
After an update of our SAP OData Service, I get the error mentioned in the subject, when I try to execute a query.
Has anyone a clue what the problem could be?
bye.