Yes, it would be great to customize this particular behavior. It really bugs me to have a space before parentheses when I'm invoking a function. A space after if, using, while, etc makes sense, but please don't put one after a function. (Interestingly, when you open up a C# Program query, the main method is written *without* the annoying space, viz. void Main().)
Well, here's one way to use it:
public static class Extensions
/// Dumps to a temporary html file and opens in the browser.
/// <param name="o">The object to display.</param>
public static void Dump<T>(this T o)
string localUrl = Path.GetTempFileName() + ".html";
using (var writer = LINQPad.Util.CreateXhtmlWriter(true))
Has anyone figured out how to get it to work when running unit tests? I am using Resharper's built-in testrunner, which has an HTML output window, but using CreateXhtmlWriter just dumps the HTML code (rather than rendering it).
Another reason for creating a LINQPad DLL (preferably without all the extra resources) is so that ClickOnce deployments can work correctly. In my case, referencing LINQPad.exe worked for development (and, I assume, installations), but I would get the following error when trying to use it with a ClickOnce deployment:
"Reference in the manifest does not match the identity of the downloaded assembly LINQPad.exe."
Also, I was wondering if there could be a way to isolate the Dump functionality without having to reference all of LINQPad - doing so increased my MSI from 600K to about 3200K :-(
Other than these issues, I am absolutely thrilled that I now have a quick, thorough tool for debugging/tracing!