LinqPad on .NET Core
It would be great for Linux and Macintosh developers to be able to use LINQPad :)
Sergei Ryabkov commented
I understand that LINQPad 6 runs on .NET Core, but only on Windows...
If you combine the following three requests, support for macOS will become the top-requested feature:
Ray Saltrelli commented
`sudo apt install linqpad` Make it happen! (please)
P.S. I'd settle for `sudo snap install linqpad` as well.
[Deleted User] commented
Will there be a .net core only lprun cli? It would be great to make linqpad scripts and run them via a linux docker container for maintance for example.
Work on a .NET Core version is underway, but to begin with it will target only Windows (.NET Core 3 Desktop). Cross-platform support may follow, but this will be a separate project and will require a review of the available cross-platform GUI libraries.
Ivan Gavryliuk commented
whatever you do please don't use Electron
Mohammed Noureldin commented
Is there any news regarding this suggestion? LINQpad 6 will support .Net Core 3.0, but will it be runnable on Linux? or is it windows only?
I also suggest to vote for this feature https://linqpad.uservoice.com/forums/18302-linqpad-feature-suggestions/suggestions/17456101-add-ability-to-target-net-core
It would be a great to have LINQ pad run cross platform on MacBook... Hoping you can get around the third party control problem you mentioned in the post.
@mortb: This is not the same as Mono support, even if both would enable you to run on OS X an Linux. Seeing as .NET Framework 4.X is now legacy and .NET Core is the way forward, I see Mono as much more of a fringe thing and .NET Core as the only way forward.
Linqpad is the only tool from Windows I am really missing from Windows for .NET development and .NET Core support and being able to run natively on OS X / Linux would be a huge win.
Any traction on this? I would be ok with just a CLI to start.
fyi - I use Fedora 28 (currently) and Visual Studio Code as an editor (not really important).
Would just need a way to do thing typically done in the UI (perhaps .linqpad/config files?) such as:
* create db connections
* install and use drivers (SQLite, etc.)
* configure external references
* reference stored queries
* CLI option to provide different output options (results, SQL, XML, etc.)
* CLI option to declare script type: C# statements, C# program, etc.
There may be other things I am not thinking of - but I believe those to be the major features.
Of course, it would be nice if it shared the same license.
I guess this is the same isssue as https://linqpad.uservoice.com/forums/18302-linqpad-feature-suggestions/suggestions/588859-support-the-mono-framework-and-run-on-osx
Justin Donohoo commented
Yes please! Would be so useful.
Michael Dahl commented
Kristian Barrett commented
I agree with this. I use LinqPad all the time, but am now moving on to OS X only, since dotnet core allows for this. I would really love to see LinqPad working on core.