Assume that a user has a PDF of your book or Skeet's book. Think of using the Nutshell and In Depth (Skeet) books as help files by linking context help (F1) in LINQPad to topics in the PDF books. If manipulating the PDF is too difficult you could load the clipboard with the appropriate page number for the topic; the user could paste the page number in the upper left box of acrobat or PDF reader is used. I like LINQPad and I have the super-duper-expensive version but I use LINQPad as a C# and NET learning tool for my programs and rarely use LINQ per se.

My suggestion is to add an optional expandable text input pane where any string could be written. This pane would be visible when choosing C# Program (or VB / F# Program) in the language drop down. The program template would then feature a Main(string arg) where the input would be fed.

Many times I find myself pasting json, xml, csv, tsv data etc into the programming pane of linqpad. Afterwards I have to put the text into a string variable and replace quoute characters and other special chars to make it compile. Sometimes I instead write the text into a file and load the file into the variable. Both solutions work and are not to hard to acheive, however it would be quicker just to paste the text into a textbox and have it readily available in the program for processing.

For me this would be a productivity feature I would use quite a lot.

When outputting a long string, LinqPad outputs line breaks not in the string after each block of 100,000 characters.

This impacts string.Dump() (with no description), Console.Write(string), and Console.WriteLine(string).

This is not just a visual issue with the output window. If you copy and paste from the output window into a text editor, the line breaks are present in the data.

string.Dump("any text") does not exhibit the problem.

Console.Write and Console.WriteLine when used in a C# console application (Visual Studio compiled) do not exhibit this behavior.

LinqPad C# Program demonstrating the behavior:

void Main()

{

"".Dump("Console.Write() has breaks at 100K chars (three lines displayed):");

Console.Write(new string('.', 250000));

Console.WriteLine();


"".Dump("Console.WriteLine() has breaks at 100K chars (three lines displayed):");

Console.WriteLine(new string('.', 250000));

"".Dump("Dump() has breaks at 100K chars (three lines displayed):");

(new string('.', 250000)).Dump();

"".Dump("Dump(\"\") has breaks at 100K chars (three lines displayed):");

(new string('.', 250000)).Dump("");

(new string('.', 250000)).Dump("No breaks with Dump(\"something\") (one line displayed)");

}

Tested on:

Windows 10 Pro
LinqPad 5 Premium v5.36.03(AnyCPU)

It would be great if replication objects and MS shipped objects could be excluded from the database object tree. I don't have the "Include System Views and SPs" option checked on the connection.

Whether it's a new option or controlled by the same include system option, it would be nice to be able to exclude objects that are ismsshipped and replication objects (that don't have ismsshipped = 1 but do start with 'sp_MS') like the examples below.

-- MSreplicationobjects
-- MSreplicationsubscriptions
-- MSsubscription_agents
select

s.name,

t.*

from sys.tables as t
join sys.schemas as s
on t.schemaid = s.schemaid
where t.ismsshipped = 1

-- Stored procedures created by transactional replication
-- Example: spMSinsdboUNITSOFMEASURE
-- spMSupddboUNITSOFMEASURE
-- spMSdeldboUNITSOFMEASURE
select *
from sys.procedures
where name like 'spMSins%'
or name like 'spMSupd%'
or name like 'spMSdel%'