LINQPad 5 supports all the new features of C# 6, including string interpolation, expression-bodied functions, exception filters,
nameof, static imports and the new 'Elvis' operator.
The new Roslyn compiler now powers both the compilation and tooling chain. This means no more edge-cases to break auto-completion!
LINQPad now fully checks your code in the background, highlighting both parsing and binding errors with red squigglies. Resolved symbols
display in turquoise, and unresolved symbols in red. Compilation is also quicker, because most of the work is done in advance.
(Pro/Premium Editions) Your code now automatically formats when closing a brace. You can also auto-format via the menu options, or the Visual Studio keyboard
shortcuts (Ctrl+E D or Ctrl+K D to format document, and Ctrl+K F to format selection).
(Pro/Premium Editions) 'Rename Symbol' refactoring is now supported. Just press F2.
(Pro/Premium Editions) You can now jump to a symbol's definition with F12. To to the reverse, and find a symbol's references, press Ctrl+Shift+Up/Down.
(The same shortcut keys also work in Visual Studio 2015.)
LINQPad 5 now uses the Roslyn VB compiler. This means all the latest VB14 features are supported, with full real-time parsing.
For Pro/Premium edition users, Visual Basic now has auto-completion, too! This includes member listings, parameter info, quick info, and as with C#,
background compilation, smart-tags, and auto-formatting. The rename-symbol feature (F2) and symbol navigation features also
work with VB.
(Pro/Premium Editions) Over 20 Visual Basic code snippets are now included. LINQPad will also pick up any that you write yourself and save in the
Visual Studio folder under My Documents, or in LINQPad's code snippets folder. Use the standard Visual Studio shortcuts
to activate snippets, or type the shortcut followed by the tab key.
LINQPad now uses FSharp.Compiler.Service. This means it longer relies on fsc.exe, although it will use fsc.exe if installed.
Parsing errors are now shown with red squigglies. Autocompletion is on the way!
In Query Properties, the Advanced tab has an option to force LINQPad to copy all non-Framework references to a single folder.
This is similar to 'Copy Local' in Visual Studio and is useful with libraries that probe for DLLs at runtime.
- There's a 'Move to New LINQPad Instance' option on the query context menu.
Recent Features and Bug Fixes - 5.0.9
- A glitch with VB autoindenting has been fixed.
- The "mscorlib 188.8.131.52" reference error when dealing with portable libraries has been fixed.
- You can customize autoformatting in Edit | Preferences | Advanced
- Holding down the Control key makes autocompletion listings translucent, as before
- Util.Run now works properly
- VB keyword capitaliztion and 'My.' properties now work propertly.
- The 'value cannot be null' error when expanding Entity Framework connections has been fixed.
- Autocompletion better recognizes delegate-typed parameters.
- The DEBUG symbol is now defined, and the UserQuery class has the same accessiblity as before.
- Object initializers now include inherited members, and auto formatting works more reliably on a closing brace.
- SQL connection errors are now correctly propagated.
- Auto code formatting now handles interpolated strings correctly.
- Renaming a type also now renames constructors and destructors.
- You now get a helpful error message if the Framework prerequisites are not met.
- The missing assembly error when running F# programs and expressions has been fixed.
The standard edition is free, as always :)
If you own a paid edition of LINQPad 4, you'll need to
purchase an upgrade
to use the paid features of LINQPad 5 (unless you purchased after January 1, 2015). You can
find out here whether
your license covers V5, and the cost of upgrading. Upgrade discounts are available until the
end of August, and further discounts are available right now to raise the user count or edition.
Your LINQPad 4 license will work temporarily with the LINQPad 5 beta (until mid August).