I'm currently considering how to enhance LINQPad to enable a command-line interface
What I need right now is an idea of exactly how people would use this feature - what are the use cases?
In particular, I need to consider how to deal with output, which is currently formatted as HTML and displayed in an embedded web browser control (or in data grids). Should this be formatted as plain text instead and directed to the console output?
For queries that require a connection, should LINQPad requery the schema and rebuild the typed data context each time you call the command-line executable (as it does currently with the GUI), or should LINQPad somehow cache the typed data context to avoid the overhead?
And how should exceptions be handled?
Edit: If LINQPad were to cache the typed data context, the cached copy would be used only if the schema hadn't changed since the last run.