236 results found
-
Support application name in SQL connection strings
I always use the SQL profiler to debug SubmitChanges issues. Using the application name argument in a sql connection string provides a very easy filter in the SQL profiler.
6 votesFrom v4.36, LINQPad adds both “LINQPad” and the query name to the application name in the connection string.
-
16 votes
LINQPad now supports both standard and code-first models.
-
add a progress bar
add a progress bar between the results button and the export results button.
Allow the currently running statements update the progress.this.Progress = ....
It can just be a number between 1 and 100, keep it simple. It will allow us to have some idea how long a query is taking.
We use linqpad for maintenance tasks as well as it's intended purpose and this would be a kewl feature.
5 votesUsage: Util.Progress = 50;
Assigning a value “hijacks” the main progress bar, turning it from a marquee into a continuous progressbar.
-
.NET Type highlighting
Highlight Types, Attributes and Classes with the Color:Teal just like in Visual Studio...
eg: DateTime should have a color
eg2: class MyClass{}
MyClass should be highlighted450 votesThis is now complete in LINQPad 5. www.linqpad.net/download.aspx/beta5
-
The ability to disable the SQL, IL and Labda output to save on memory consumption.
The ability to disable the generated SQL, IL and Labda output to save on memory consumption for large queries.
4 votesYou can disable SQL translation generation as follows:
ExecutionEngine.SqlTranslationsEnabled = false;
The Lambda translation window shows output only for queries that you dump, so it shouldn’t consume memory out of tandem with the results itself. Let me know if you think this is still a problem.
The IL translation only populates when you actually click on the tab.
-
recover unsaved queries after failure
provide for recovering unsaved queries when LINQPad stops working
4 votes -
1 vote
A bug that sometimes prevented this from showing has been fixed in 4.36
-
recover open files after computer crash
My workstation crashed (not LinqPads fault!), but I did have a few queries open. It would be nice if LinqPad would offer me to recover those files (exactly like Word, Visual Studio and even SQL Management Studio).
But yeah... I should have saved those files...5 votes -
Regions & Outlines
I'd like regions (#region, #endregion) to behave as in Visual Studio so I can expand and collapse them. So far they don't appear to.
1 voteThis feature is available with the registered version, in ‘C# Program’ mode.
-
AutoComplete for F#
AutoComplete for F#. Also looking for F# Samples.
55 votes -
Go to definition
Would be great to have the functionality like we do in Visual Studio to right click a method call and go to the definition of the method in the query window. Sometimes I work on rather large linqpad scripts and this would be very handy.
39 votesThis functionality is available in LINQPad 5
-
Automatically Switch From Expression to Statement(s)
Upon detecting multiple statements: Automatically switch Language from Expression to Statement(s) for selected language.
26 votesThis is available from version 5.24
-
Dump to file
Instead of requiring excel or word installed on the client's machine, what the output could be dumped in csv format?
Copy/Pasting from the html output is not effective.
12 votesThere are now methods in LINQPad’s Util class to do this (ToCsvString, WriteCsv, ToHtmlString, CreateXthmlWriter, etc).
-
Path to current script
Would like to get the path of the currently executing linq script.
3 votesThis feature is available from v4.27.1.
Util.CurrentQueryPath now returns a full path to the current query.
-
Allow extension methods returning local types
As per the "allow extension snippets" suggestion, extension snippets are now permitted. However, these do not work if they reference a local type.
Example:
void Main()
{
new Local().AddFoo().Dump();
}public class Local {}
public static class Extensions
{
// The type or namespace name 'Local' could not be found
public static string AddFoo(this Local local)
{
return local.ToString() + "Foo";
}
}2 votesThis is now fixed.
-
support for reactive extensions
support IObservable to be Dumped. Have a look at http://naveensrinivasan.com/2010/04/07/using-odata-linqpad-reactive-extensions-rx-to-query-stackoverflow/
0 votes -
Add Entity Framework support for Code First
The Entity Framework support currently requires the different xml files; EF will support Code First (currently in features CTP 3) which is all code, no xml files. It would be great to have LINQPad allow for EF Contexts using Code First.
75 votesLINQPad now supports both standard and code-first models.
-
Dump more than 1000 items
The overloads of Dump() affect depth of the object graph, but not width of dumped data. It would be useful to be able to Dump x number of items from any IEnumerable, including all items.
4 votesDone. Click the ‘Results in Grid’ icon and the result count is limited only by memory.
-
An option to automatically scroll to the end of the Results Window after a query
My interesting information is always at the end. So it seems unneccessary to be forced to scroll the Results window after every query.
3 votesCompleted in 4.35 – Shift+Control+E is the shortcut to toggle this
-
Auto Scroll Results
When processing, say a folder of files, it would be nice if the Results window would have the option to auto-scroll the results as they are Dumped.
6 votesCompleted in 4.36. Go to Query menu – Shift+Control+E is the shortcut to toggle this.
- Don't see your idea?