3 ms·

There is an alternative of LinqPad. It does not have a lot of features, but it is good enough for testing code snippets. https://github.com/roslynpad/roslynpad

There is an alternative of LinqPad. It does not have a lot of features, but it is good enough for testing code snippets. https://github.com/roslynpad/roslynpad https://github.com/roslynpad/roslynpad

xnorswap 2y ago
When it comes to C# REPLs I absolutely adore LinqPad, although recently it's felt like I've had to buy licenses for it increasingly often which I've found annoying. If any other REPL can get to a point where it can rival LinqPad in functionality then it'll be an absolute winner. The key features linqpad has that I'd need from any replacement: * Securely store secrets Util.GetPassword prompts the user for the password if it's not in it's store. Leverages the windows user credential store. * Keeps the process running This is absolutely key, it keeps alive the process even after the script has finished, so you can easily attach a debugger / profiler to it when the script isn't running, then start the script again. It also means you can use AppDomain.CurrentDomain.SetData to cache expensive setup if you're trying to profile something. * Quickly switch between expression / statements / program mode It'll intelligently work out if you've written a single expression vs multi-line statements, and you can switch to "program" and it'll wrap what you've done so far in a Main stub. * Easily define default App.Config files, default namespaces, default nuget packages. After finally getting a fiddly setup working, there's a "Use as default for new queries" button which is very convenient. Also the "clone query" functionality is similarly useful for copying not just the C# text but all the background namespace declarations, references, config, etc. And that's about it. I barely use the database connection and exploration side, but I do use it daily for hooking into DLLs to quickly test changes to our internal projects.
- stanac 2y ago
  RoslynPad support user input with `Console.ReadLine()`, but that's about it. For me personally it does everything I need for scripting C#. For anything more serous I usually create full program and a bat/sh file to execute it in a conveniently.
- hnrodey 2y ago
  Great to see LINQPad getting some love. Wish it had a fully functional trial so outsiders can see the real thing before paying. Otherwise, the free version is crippled and boring. Made this video to show LINQPad and getting OAuth tokens from the Spotify api. https://www.youtube.com/watch?v=g2C1SXfTHXI&t=30s https://www.youtube.com/watch?v=g2C1SXfTHXI&t=30s

There is an alternative of LinqPad. It does not have a lot of features, but it is good enough for testing code snippets. https://github.com/roslynpad/roslynpad https://github.com/roslynpad/roslynpad

xnorswap 2y ago

When it comes to C# REPLs I absolutely adore LinqPad, although recently it's felt like I've had to buy licenses for it increasingly often which I've found annoying. If any other REPL can get to a point where it can rival LinqPad in functionality then it'll be an absolute winner. The key features linqpad has that I'd need from any replacement: * Securely store secrets Util.GetPassword prompts the user for the password if it's not in it's store. Leverages the windows user credential store. * Keeps the process running This is absolutely key, it keeps alive the process even after the script has finished, so you can easily attach a debugger / profiler to it when the script isn't running, then start the script again. It also means you can use AppDomain.CurrentDomain.SetData to cache expensive setup if you're trying to profile something. * Quickly switch between expression / statements / program mode It'll intelligently work out if you've written a single expression vs multi-line statements, and you can switch to "program" and it'll wrap what you've done so far in a Main stub. * Easily define default App.Config files, default namespaces, default nuget packages. After finally getting a fiddly setup working, there's a "Use as default for new queries" button which is very convenient. Also the "clone query" functionality is similarly useful for copying not just the C# text but all the background namespace declarations, references, config, etc. And that's about it. I barely use the database connection and exploration side, but I do use it daily for hooking into DLLs to quickly test changes to our internal projects.

stanac 2y ago
RoslynPad support user input with `Console.ReadLine()`, but that's about it. For me personally it does everything I need for scripting C#. For anything more serous I usually create full program and a bat/sh file to execute it in a conveniently.
hnrodey 2y ago
Great to see LINQPad getting some love. Wish it had a fully functional trial so outsiders can see the real thing before paying. Otherwise, the free version is crippled and boring. Made this video to show LINQPad and getting OAuth tokens from the Spotify api. https://www.youtube.com/watch?v=g2C1SXfTHXI&t=30s https://www.youtube.com/watch?v=g2C1SXfTHXI&t=30s