I need some feedback on this feature. First:
(a) Would you expect it to apply only to untitled queries? Or:
(b) Would you also expect it to apply to saved queries that were modified?
(The reason I ask is that option (a) is simple to implement, whereas option (b) creates numerous complications.)
814 votesFranklin Ross commented
As Erling mentioned, would it be easier to just compile the referenced query and add it as a reference behind the scenes somewhere? Just add 'using static MyQueries.QueryName' on the references tab or something. This would import all static members and types, which would achieve the same thing. I know Joe Albahari has mentioned there are plenty of complicated issues with a C style #include, but for the most part I just want this to get at types I can reuse across queries.
1,453 votesFranklin Ross commented
This would be great! I've been thinking about this for a while because I pretty frequently write little LINQPad scripts for pulling some data out of a few files or a DB for a non-tech. Being able to create an exe that I can give them to run themselves would be great.
I'm currently seeing how I go writing a mini UI library for easily prompting the user for some inputs in a LINQPady kind of way, like 2 file open dialogs for instance (or whatever). Ideally the same exe would be able to parse command line arguments for the inputs too. We'll see how I go (I just started), but this suggestion would complete that whole thought into a quick tool creator.