236 results found
-
Skip Highlighting when dumping to Grid
There should be away of preventing Highlight / HighlightIf from working when dumping to Grid. At present they just confuse the output (you read the 'raw' value for all the HighlightIf=false rows, but 'object' for all the HighlightIf=true rows)
If there were a 'DumpContext.Mode' then obviously that could be used as part of the HighlightIf predicate. But there isn't (that I know of). And it can't be query-wide because different parts of a query might be dumped differently (does have to be some kind of dump context).
1 vote -
Allow active hyperlinks in comments
So that a comment beginning with http... could become clickable and launch the default browser.
1 vote -
Entity Framework 7 support
Add support for EF 7 from ASP.NET 5 projects
9 votesLINQPad supports EF7 from 5.06 onwards.
-
Self updating LINQPad
Any new version of the LINQPad should be downloaded manually. Most of the modern apps provide self updating option. With tools like https://github.com/Squirrel/Squirrel.Windows. It would be great and that would avoid checking for new releases.
3 votesLINQPad has always been self-updating, from day 1.
-
Only have one Ctrl+Shift+M shortcut
Ctrl+Shift+M was Copy for Markdown/StackOverflow, but a recent update has also made it Namespace Imports.
I'd like to keep it as Copy for Markdown/StackOverflow and change Namespace Imports.
0 votes -
Add a Refresh() method to DumpContainer
Currently I need to do:
var dc = new DumpContainer{ Content = x }.Dump();
// ...later, x changes...
dc.Content = null; // Otherwise it doesn't notice the new assignment.
dc.Content = x;3 votesA Refresh method on DumpContainer has always existed.
-
3 votes
This is already allowed in LINQPad 5. Press F4, and in namespace imports, prefix the namespace with ‘static’. For example, “static System.Console”.
-
Allow to disable the default namespace inclusion
It is annoying that I always have to fully qualify "System.Transactions.IsolationLevel" because of the conflict with "System.Data.IsolationLevel".
1 voteYou can now remove any of the default namespaces in LINQPad 6.
-
1 vote
-
Monitor open files for external changes and prompt to reload
Linqpad should monitor open files and prompt the user to reload them if an external process updates them, such as git/source control updating the file.
18 votesThis is supported from LINQPad 5.38 and in LINQPad 6.
-
3 votes
Ctrl+MouseWheel or Ctrl+[ / Ctrl+] (see Edit | Preferences)
-
NuGet v3.0 support
Allow upgrading LINQPad NuGet package to 3.0 independently
21 votesThis has been supported for some time
-
Add C# 6 support
It would mean upgrading to 4.6, but that's not a bad idea anyways.
1 voteGo to www.linqpad.net/download.aspx and download LINQPad 5
-
LINQPad 5 bug - can't use XmlSerializer
Use of XmlSerializer in LINQPad 5 is not possible. Serialization ends with "UserQuery is inaccessible due to its protection level. Only public types can be processed" exception. In V4 there is no problem.
1 voteThanks – this is now fixed in the new beta:
http://www.linqpad.net/download.aspx#beta5 -
Highlight same word currently in pointer on all document; like VS does.
Highlight same word currently in pointer on all document; like VS does.
18 votesThis is available for symbols, from version 5.24
-
Highlight same text as selected in editor
Just like in Visual Studio (and MANY other editors):
When you select some text in the editor, the same text gets highlighted. This helps the developer identify errors and places that needs to be changed / refactored etc..32 votesThis is available for symbols, from version 5.24
-
Add a confirmation dialog before deleting a connection
I was attempting to refresh a connection in the connections list window and I accidentally deleted the connection. No confirmation dialog popped up, just woosh, connection gone.
Which is fine, I can just re-add it once I figure out the connection string details again ( I have a lot of connections in there).
Just a small annoyance. (Large annoyance for users with lots of connections)
1 voteCompleted for next beta.
-
Support for C# 6 Language Features
C# 6.0 is currently in Preview with Visual Studio 2015 preview. As I am starting to use the newest version of VS, I am exploring the behavior of the new language features, including the new nameof operator, string interpolation, the null conditional operator, index initializers, etc. I instinctively go to LINQPad to test something out including these but then realize it is not yet supported :(
37 votesLINQPad 5 with C# 6 and VB 14 language support has now been released.
-
Make explicit whether LINQPad is running as 64- or 32-bit.
I get the dreaded 'An attempt was made to load a program with an incorrect format... ' error, which usually means that I'm trying to load an assembly compiled for 64-bit in a 32-bit environment. However, there's no explicit way to see this in LINQPad. It could be shown in the 'About' window.
36 votesThis features is available from 6.9.x
-
Sharing code across LINQPad queries
At present, the only way to share code across LINQPad queries is to put them in "My Extensions" but this causes the code to be available to ALL queries, and it would be good if this could be specified on a more granular basis, where the code is shared with only a subset of queries.
For example, in my queries folder, if I'm working on ACME API, I'll have a folder called "ACME API" with separate files for whatever I'm working with - eg. get-user.linq, add-product.linq.
It would be good if I could create a file called common.linq (or something…
35 votesThis is now available in LINQPad 6:
https://www.linqpad.net/LINQPad6.aspx
- Don't see your idea?