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.)
I would like "Notepad++" approach too - reopen tabs as they was before closing. It's simple and intuitive, for use as scratchpad with autosave feature too. Same here - often i do some code tests in Linqpad, with multiple important code fragments opened in different unsaved queries. OK, there is bruteforce 'end task' solution, but it is inconvenient and also it doesn't work for windows insider 'fast ring' machine due to frequent OS updates. At least, if possible - keep unsaved (new and untitled) queries …
In addition to previous:
Of course, debug-time access to variables, properies and methods, like immediate window functionality, is a MUST thing, due to poorly immediate window functionality.
And so on ...
Great idea! But this can be very complicated thing. In fact, to be useful, that addin MUST get NS references from current project, as well independently parse project code, even not yet compiled, ability to access not public members would be welcome. As result we can not to always do 'copy - paste - edit - adjust - test' cycle, but, for example, simply type in LinqPAD pane something like "new SampleClass.SomeProtectedMethod(anything)"....
In this situation you don't need more copy back corrected code fragments, they will be already edited inplace!
But likely this is too nice to be truth .... :(
However, this can be GREAT value for what i'll want to pay, much more than autocomplete in LinqPAD standalone version.....
8 votesRaimonds shared this idea ·