529 votesklmcw commented
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.
244 votesklmcw commented
I have tried the suggestions at http://www.linqpad.net/PortableDeployment.aspx and when running with the dotnet cli on macOS Sierra I get:
The library 'libhostpolicy.dylib' required to execute the application was not found...
So I guess portability only extends to the various Windows platforms. Is that right?klmcw supported this idea ·