Setup Custom Visualizer to always display after every/any query is run?
Looking at building a custom visualizer per this documentation - https://www.linqpad.net/customvisualizers.aspx
Do we have an option/way for a custom visualizer that will appear after every query execution similar to how we already see the Output, SQL, IL, Tree, AI, etc. tabs.? Other than the initial setup to make the visualizer code available either from My Extensions or placing a custom dll file in the requisite directory for LINQPad to discover...
Looks like the user must always initiate the visualizer through some form of dumping an object.
This is pretty close to what I want but even still this package requires the user to dump an IQueryable to see the custom visualizer window. https://github.com/Giorgi/LINQPad.QueryPlanVisualizer/tree/main
Please let me know your thoughts.
Comments
Can you provide an example of what you'd like to achieve?
I think what he's trying to achieve is effectively make a plugin/extension to LINQpad to always include a new tab to show the query plan, alongside the results and raw SQL tabs among others. Currently, we'd have to dump the new panel to display that tab in the first place, so it's driven by the script itself. Maybe a way to execute something before any script is run might be enough?
A plugin system in general would be nice to have, to make LINQpad more extensible.
@JeffMercado nailed it. That's precisely what I'm trying to achieve. Additional panel windows irrespective of my script needing to initiate the Dump.
In my case, I want source control (Git) handling of my scripts directly within LINQPad. I'm building a source control panel and it's just a little clumsy if I need to update each script to output the window. I want the source control window in perpetuity.
Today, I use VS Code opened to my Queries folder for the Git tab. It works but it's clumsy.
What process would the code driving this window run in? For source control, it sounds like it would need to be independent of the script. And what data and events would it need access to? Would you envisage using HTML or WPF for the UI?