1182 results found
-
Enhancement of autcomplete on subqueries
When writing for example:
from u in Users
select new
{
UserDetails = (from ud in ....
}When I press "u" I would expect u as the alias for Users in the outer query, but it picks up everything.
4 votes -
Query Properties Profiles
Query Properties - Profiles
Set and save different Profiles for query properties. We have different code branches for development and release cycles. It would be great if I could setup and switch between different profiles for a LINQ script.
4 votes -
SQL table direct editing: Leave mode, and ask before saving row changes
I like the ease of directly editing SQL tables in the premium edition. However, it's a little too "eager" to save for my taste. I'd like to suggest a couple related changes to make it safer for a klutz like me to use without accidentally nuking things:
1) LP has the new "Edit" button, but not an "End Editing" button.
2) When clicking between rows, any changes to the row being "blurred" (moved away from) are automatically saved. It seems like it should be asking first, at least once.Combined, these two things would make it much safer.
4 votes -
Save As.. = Ctrl+Alt+S
New shortcut for "Save As" command.
4 votes -
Make it possible to call WinRT APIs from LinqPad
As explained here: http://www.hanselman.com/blog/HowToCallWinRTAPIsInWindows8FromCDesktopApplicationsWinRTDiagram.aspx
I often use LinqPad to test small pieces of code, but I can't do it when this code depends on WinRT APIs...
4 votes -
Dump collections as each item is processed
Every so often, I would be running a long running query that yields many results. And every once in a while, when dumping the results, there is a failure because of some exception (e.g., OutOfMemoryException, NullReferenceException, etc.) and you never see any of the results because of that. The dump method only writes to the results until the entire collection has been processed and renders them all at once.
It would be nice if LINQPad would dump each item as the collection was being processed so in the event of a failure, we could see the results that have been…
4 votes -
Step by step wizard to create linq query
Most of the times Pivot tables are used for Data Visualization/Graph. Would like to see wizard that can help you creating pivot table.
4 votes -
As a driver developer, I want to include 16x16 icons that override the default ExplorerIcons.
For example, if I am working on (hypothetical) HTTP/REST-based driver, I would l like icons that read GET, HEAD, POST, etc. next to the url path that would be displayed as the ExplorerItem text.
4 votes -
Interop among queries (and languages) inside LINQPad
For example, I have a query with code written in F#. Then I can reference this query in a C# query and use the functions that I wrote in the F# query. So, that is not necessary to open Visual Studio, create a F# project write the code then compile it to a .dll and then reference that assembly in a C# query in LINQPad,
4 votes -
Column Mode and status bar informations
Add support to Column Mode ("Shift + Alt" in Visual Studio) and show the Ln, Cols and Ch information in status bar like in Visual Studio.
When I need do a substring in a line of text, I need use other editors (like Notepad++ or even Visual Studio himself) to know which position of chars.
4 votes -
Include additional databases (linked) servers INFORMATION_SCHEMA
When including additional databases from (linked) servers, the INFORMATION_SCHEMA views from the linked database should be included.
We can then use LINQPad to compare schemas between databases.4 votes -
Support Console output e.g. Backspace /b etc
int updateCount = 343;
for( int i = 0 ; i < updateCount ; i++ ){
string msg = string.Format( "Update Progess:{0:p}" , (double)i/(updateCount-1) );
Console.Write( msg );
Console.Write( new string( '\b' , msg.Length ));
}
Console.WriteLine();4 votes -
feature
I'd like linqpad to save all open queries when closed. Similar to how it recovers unsaved queries after crashing. If I've changed 'Named' queries it would prompt to save changes, but unnamed queries are just saved without a dialog.
I often have numerous ad-hoc queries I've written over the course of a day and are specific to what ever issue is the daily crisis.
Also auto language detection would be nice as well; C# Vb ect.
4 votes -
Add option to open Data Grids in Edit Mode
When cleaning up a lot of data by hand, it gets very tiresome to have to click 'Edit Data' on every table. It would be very useful, and save a lot of time and stress on one's wrist, to be able to have tables open already in edit mode.
4 votes -
bing codesnippet search support in linqpad (http://codesnippet.research.microsoft.com/)
Bind codesnippet search is awesome to look for code snippet for specific problems...
4 votes -
Disable my extensions in query properties
Add an option to the query properties to disable "My Extensions" for a specific query.
The problem with "My Extensions" is it can bring in unwanted references. For example, I have extensions that use Newtonsoft.Json, and wanted to run a query without a reference to that dll. The only way I could achieve this was by removing it from "My Extensions". It is awkward to have to edit "My Extensions" and remove all the references and functions just to run a single query, then have to add them all back afterwards.
4 votes -
add a dark theme
i find dark themed environments a lot more comfortable to work in. That's why almost all IDE's have them as an option.
4 votes -
Add support for "select *" to autocomplete in C#
When I type "select new { t1.", it gives me the option "(press ` to select multiple items). I would also like the option "(press * to select all items)", it would then insert all field names for the table, in the original order.
4 votes -
Add Alt+Enter shortcut to pop up the auto-suggestion drop down (a la Resharper)
When I enter a class name from a namespace that isn't referenced, a little auto-suggestion hint appears. In VS+R# I would hit Alt+Enter to open this menu, and then Enter to accept.
In LinqPad I have to use the mouse to do this.
4 votes -
Stop linqpad from querying __MigrationHistory on each call
EF queries the __MigrationHistory each time the DbContext is opened to ensure the DB context is in sync with the DB. This can be very expensive. Can LinqPad provide an option to skip this check by doing Database.SetInitializer<UserQuery>(null)?
UserQuery seems to be the class that gets derived from the user created DbContext.
4 votes
- Don't see your idea?