LINQPad Debugger - Early Input Request!
What are your thoughts on integrated debugging within LINQPad?
- What features in Visual Studio's debugger do you consider important / unimportant for LINQPad?
- What unique/original/outside-the-box debugging features could fit well with LINQPad? For instance, would the ability to send any local variable to the Dump pipeline be useful?
- Debugger support requires that LINQPad shifts from an AppDomain-isolation model to a process-isolation model. The performance cost on today's hardware is minimal, but there will be subtle changes in how queries execute. Mostly good (StackOverflowException will not take down the host, the current directory would be stable and locked to the query's path, etc). Your thoughts?
- Funding: would you pay extra for this functionality? The development cost to get this to production quality is maybe 3-4 man-months with late nights