1 complement, 1 question and 1 idea
Hi, my name is Bryan. I have been using LinqPad since the invention of the hammer. This application is paramount in my daily life. Not only do I use is professionally, I also use it personally and I have recommended this application countless times and lead to several purchases, a few enterprise level at different companies I've worked for.
This application is amazing and the quality grade A.
I've seen some questions on the forum and the internet in general about user input. Generally I've seen people use VB references and the Interaction.InputBox method. Is there any other methods for user input? If not are there any plans for user input?
I have created queries that start small and over time become pretty complex and in some cases have a decision tree that needs input from the user. A simple example would be a combo box list of several choices. I'd like to prompt the user (typically always me) for the option and have the query adjust based on that choice.
If needed I can elaborate and give a real world example.
Which leads me to an idea or suggestion that might be something for a future build. First, is it possible to create plugin's for LinPad? Or better yet, does LinPad support MEF or any other type of dependency injection and if so could some of it's core functionality be modified? I understand there could be some security concerns around the world creating plug-ins that might touch or transmit data. Maybe some type of "Verified Plug-In" where the code has been reviewed by a community. Anyway, that's a side tangent.
My suggestion/request - as I stated before some of my queries become very complex - practically mini-applications. THAT said, it would be nice if there is a way to "promote" this query into an application. Press a button and it extract program.cs with a data context and table classes, config file with the connection string, etc-
Anyway, thanks for your time.
~Bryan
This application is amazing and the quality grade A.
I've seen some questions on the forum and the internet in general about user input. Generally I've seen people use VB references and the Interaction.InputBox method. Is there any other methods for user input? If not are there any plans for user input?
I have created queries that start small and over time become pretty complex and in some cases have a decision tree that needs input from the user. A simple example would be a combo box list of several choices. I'd like to prompt the user (typically always me) for the option and have the query adjust based on that choice.
If needed I can elaborate and give a real world example.
Which leads me to an idea or suggestion that might be something for a future build. First, is it possible to create plugin's for LinPad? Or better yet, does LinPad support MEF or any other type of dependency injection and if so could some of it's core functionality be modified? I understand there could be some security concerns around the world creating plug-ins that might touch or transmit data. Maybe some type of "Verified Plug-In" where the code has been reviewed by a community. Anyway, that's a side tangent.
My suggestion/request - as I stated before some of my queries become very complex - practically mini-applications. THAT said, it would be nice if there is a way to "promote" this query into an application. Press a button and it extract program.cs with a data context and table classes, config file with the connection string, etc-
"This thing has outgrown LinqPad, I need to promote!"I would appreciate some feedback from the developer and other community members.
- click promote button
- file save location prompt
- exports all the files needed, in the format selected (C#,VB)
- opens windows explorer to the location with all the files
- bonus bad-ass points awarded if it creates a VS project file (or an option for users who don't use VS)
Anyway, thanks for your time.
~Bryan
Comments
Util.ReadLine()
method?
Or if you really want a dialog:
You could create your own method to mark up and display a combobox and save it in MyExtensions:
Regarding extensibility points, these are hard to design (and easy to screw up) without a reasonable set of use-cases.
You're right about Util.ReadLine being clunky. When you provide it with suggestions, it feeds the autocompletion list, but it doesn't give a combobox dropdown, so there's no way to get a list of all options. I'll fix this for the next build.