Best Of

If you reference a NuGet package with content files, LINQPad will recursively copy the following folders automatically:

contentFiles\any
contentFiles\cs

Otherwise, you could use LINQPad's OnInit hook method and write a query like this:

void Main()
{
    // Test it:
    Util.Cmd (@"dir");
    Util.Cmd (@"dir foo");
}

void OnInit()    // Executes when the query process first loads
{
    if (!Directory.Exists ("foo"))
    {
        Directory.CreateDirectory ("foo");
        File.WriteAllText (@"foo\\test.txt", "test");
    }
}

To re-use this from another query, save it to a query such as "foo.linq", then #load it as follows:

#load "foo"

void Main()
{
    // Test it:
    Util.Cmd (@"dir");
    Util.Cmd (@"dir foo");
}

Try the following:
https://www.bennadel.com/blog/1095-maintaining-line-breaks-in-an-html-excel-file.htm

...Util.RawHtml (....Replace ("<br />", "<br style='mso-data-placement:same-cell;'>"

Yes, and it should also pick up other directives such as #define, #undef and #LINQPad. I'll get this fixed.

It's on the list, but it's non-trivial because a proper implementation would allow it to continue running in the background, i.e., when the dialog has closed.

A beta is now out:
https://www.linqpad.net/linqpad6.aspx#beta

You can now override the login's domain with a different AD domain or tenant ID in the connection dialog.

Let me know how you get along.

In the next build, you'll be able to do this:

from file in new DirectoryInfo (Util.LINQPadFolder).GetFiles()
select Util.HighlightIf (
    file.Extension == ".exe",
    new
    {
        file.Name,
        file.Length,
        file.LastWriteTime
    })

and this:

from file in new DirectoryInfo (Util.LINQPadFolder).GetFiles()
select new
{
    Name = Util.Highlight (file.Name,
        file.Extension == ".exe" ? "yellow" :
        file.Extension == ".dll" ? "lightgreen" :
        null),  // null = no highlight
    file.Length,
    file.LastWriteTime
};

Thanks - I'll get a beta out soon.

Try Path.GetDirectoryName(Assembly.GetExecutingAssembly().Location)

By default, LINQPad works like a Visual Studio 2019 library project in this regard: only the output DLL is copied to the output folder, and NuGet dependencies are picked up on the fly from the NuGet folders.

You can ask LINQPad to copy all dependencies to the output folder by ticking the checkbox in Query Properties > Advanced.

There's also a button on the Query Properties dialog "Export all DLLs to folder". This will create a temporary folder containing all the dependencies and then open the folder in Windows Explorer.

I can use xUnit with xUnit test runner successfully with LinqPad 5, but it fails to run with LinqPad 6. Details can be found at StackOverflow. Trying to replace the xUnit by a .NET Core version didn't help, the issue seems to be with the test runner. How can that be fixed?