Settings and activity
5 results found
-
129 votes
An error occurred while saving the comment -
1,681 votes
Jason DiOrio supported this idea ·
-
51 votes
-
255 votes
An error occurred while saving the comment Adding 3rd party support for languages either like the driver system for data access or the plugin system for custom visualizers would be pretty cool, though I don't know if there's enough people writing new CLI languages for it to be adopted by others. Personally I like the idea of supporting C++/CLI (the replacement for Managed C++) and I'm sure other languages would be great (maybe even powershell, supported by a custom visualizer), but it seems like it might take a while for all of these to be implemented individually so maybe an exposed API might be well liked. For all I know it could already exist :S
-
84 votes
An error occurred while saving the comment This sounds like a super cool idea, but there are a lot of different ways I can think of writing such a thing, each with different pros and cons. In the application itself, a streaming console of code/output would be relatively simple to reuse already created UI.
Slimming it down and making it more like a console in the terms of having some aliases/shortcuts for navigation (like directories) and making it easy to run scripts from those locations would be varying in difficulty depending on how easy you want it to be out of box.
A really nice console accessible shell (something you could use through SSH as an example) would likely be much more complicated and likely outside the scope of this project, though I love the idea of new shells. It could, at best, take on a similar model in terms of using extension methods and dynamic compilation, but the IO (and user experience), which is a huge part of LINQPad would be completely different in ways that would be difficult to share much implementation. I feel like voting on this is a pipe dream for me, but I'll take it if you want to give it :D
It would also be nice to have support for "set deadlock_priority low;" since any ad hoc queries we do don't want to get in production's way. I'm currently working on a workaround for this, but it would be nice to have it build into the context in some way.