236 results found
-
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 -
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.
-
Add tooltips on columns in schema view to indicate length
It would be nice to see a tooltip pop up over a column in the treeview on the left indicating the SQL type and maximum length (e.g 100 characters)
4 votesIt’s now in the latest release.
-
Enhance performance of expanding a database.
One of the systems I work on is Microsoft Great Plains, it has over 30,000 stored procedures and expanding the database to start a query takes a very long time (minutes).
4 votesThe performance with large schemas has improved considerably from V2.0, so you might find it’s OK now. If not, you can uncheck ‘Include SPs and Functions’ in the connection info to prevent LP from loading the stored procs.
-
At least allow changing of the editor windows background color? (pure white bothers my eyes)
While I don't expect to allow changing of all of the code coloring elements, at least just allowing the change of the background color of the editor window would be nice (I prefer a slightly off-tan color for example)
4 votesYou can set the editor background color from v2.22.1 in Edit | Preferences. I’ve also tweaked the text color set for dark backgrounds – let me know your thoughts.
-
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.
-
recover unsaved queries after failure
provide for recovering unsaved queries when LINQPad stops working
4 votes -
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.
-
Add Table.Where(...) to context menu
When you right-click a table on the connection tree on the left, it gives the following options: [Table].Take(50), [Table].Take(...), [Table].Count(), and from x in Table where ... select x.
It would be nice to add a [Table].Where(...) option there to short-hand a standard Where() command start in the query window.4 votesCompleted in 4.37
-
Fix the SQL Server Manager open file bug
When I click "Open In SQL Management Studio", I have the following reply from SSMS - translated from French:
The following files were specified on the command line:
D:\Documents
and
Settings\
...
\bbsilkof.sqlThese files couldn't be found and won't be loaded
I suppose you should add enclosing quotes to the file name when emitting the command line. This should fix this.
3 votes -
Add textbox to 'Add References' dialog
Add Reference dialog :
- add textbox for easier searching so you see what you type
- searching should be done using filtering, all results containing the search argument,not starting with
eg searching for Web should give : System.Web, System.Web.Mvc etc3 votesCompleted in latest build. There are other enhancements to adding references, too (see
Help | “What’s New”) -
Language regions
Hi,
would be nice if in the editor u can define regions for
the diffrent language types.Example:
SQL
SELECT 1endregion
LINQ-Statments
var x = from a in {1,2} select a;endregion
C#-Programm
void Main() { var x = from a in {1,2} select a; }endregion
If u enter one region it could be executedt.
If u mark more then one region (for example 3)
the output window should render 3 vertical outputs.3 votesThe latest build allows regions in ‘Program’ mode.
-
Support ADO.Net providers that contain EF implementations
ADO.Net is a provider model (factories). You can load and query the provider to see if it supports EF. That is the whole point of having ADO.Net as a provider. Adding each provider one at a time means a lot of hand coding per provider. It would seem to be a better use of your time to just support ADO.Net and the provider model.
This would allow you to use VistaDB, Sqlite, Oracle, MySql, etc as long as they have an EF provider that supports the provider factory correctly.
3 votesYou can specify any provider and connection string from V2. Please note that this only works with static DataContexts – i.e., EDMs that you’ve defined yourself in VS. It’s not possible to do otherwise AFAIK there’s no general and reliable way to query schema via EF and ADO.NET.
-
Collapsible Regions
I use SSMS quite a lot for queries that I use often. One missing feature in SSMS is collapsible regions, but there is a plugin for doing that. This has made canned queries that I use often more easy. It would be nice to have something like that in LinqPad. It would be handy to be able for instance to create canned queries that have a few variables at the top and a region of query code that is collapsed so that it is easier to look at and harder to mess up the code by accident.
3 votesThe latest build allows regions in ‘Program’ mode.
-
Tuple support
Support Tuples - probably necessary to effectively keep-up with VS2010
3 votesDownload LINQPad 4.x
-
BUG: Clone Query, Query Properties are duplicated
I have some default namespace imports set up.
When I use the "Clone Query" feature, then check the new query's "Query Properties", the namespaces are listed twice.3 votes -
Cache executed LINQ commands
When a LINQ query is executed, it appears LINQPad compiles and executes the expression each time. If the query is executed a second time without any modification, the full performance hit of the recompile still occurs. Caching the compiled LINQ would improve performance significantly; the cache value could be invalidated if the query changed.
3 votesCompleted in 4.36
-
Your latest autocomplete for lambda expressions is kind of annoying (and at times irritating)
Please provide option to disable it
3 votesAn option was added to disable this in v2.1. Go to Edit | Preferences
-
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
-
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.
- Don't see your idea?