1205 results found
-
Allow context constructor with optional parameters
We make use of optional parameters in the constructor of our typed datacontext. However, LINQPad cannot consume this datacontext. I get an error: "The type must define a public parameterless constructor." I propose that if there is a constructor with optional parameters and default values, that constructor should be used with the defaults.
3 votes -
Give preference option to set default fetching count than 100
I'd like to fetch 10 items rather than 100 as 100 items make me to scroll to top always.
It would be good to adjust default fetch count in Preference.
2 votes -
change var to specific type
Resharper gives handy feature that can change var to specific type.
Linqpad already gives (knows) what var type is. So, it would be good to have a feature to change var to specific type in Edit > Refactoring menu.3 votes -
Allow Tagging the queries for better Organization
As a reference provider I would like to label/tag queries so that it is easy for others to locate queries using tag/labels.
I am using folders to organize my saved queries by creating folder for language, type, version, library used etc. These queries are examples of how to use different libraries or language features. I organize these by creating folders for Libraries or Features used in the query.You can imagine that some queries include multiple libraries plus language features, in which case it becomes difficult to decide where to place it or end up in coping the query in many…
6 votes -
Dump() not generating navigation properties for large tables
When querying a table with a large number of columns, navigation properties are not appended to the table.
In particular, Table A I'm querying has 41 columns and does not produce the navigation properties.
Table B with 29 columns does produce the navigation properties.
We have a 1:Many (one table B for many table A). The link from TableB -> TableA does show, and it's not an issue with foreign keys, I suspect it's a hard limit we've crossed excluding the properties from generating
24 votes -
Add LINQPad to the Windows Store
Microsoft has released their Desktop App Converter (see https://developer.microsoft.com/en-us/windows/bridges/desktop) that allows Win32 apps to be published in the Windows Store. It would be great to be able to install and update LINQPad from the Windows Store.
13 votes -
Connect to a sql backup file
To be able to connect to .bak file, SQL Server backup file, would be totally amazing
6 votes -
Support VSTS Package Management Service
We use VSTS PMS, but LinqPad NuGet Manager can't correct login.
51 votes -
Add a windows explorer context menu "create linqpad snippet" for .dlls
Add a windows explorer menu short cut that would :
When right clicking assembly files (*.dll) which are .net dlls
startup linqpad with an empty snippet that has the dll as reference.
Ultimately linqpad would reflect the public members of the dll and list them somwher in the left pane.For trying out dlls this would be a killer feature!
You could also implement "spying" on configuration manager so that any calls to ConfigurationManager.AppSettings would alert the user and let him enter a value that the snippet would use.
3 votes -
Keep history of results, or simple append new results
I use LINQPad for computation. From time to time I need to change a few parameters and re-run the query. Now I have to export results to files then do the comparison.
It'd be nice to give an option to APPEND results instead of CLEAR OLD + NEW. (I can write a line to the output to separate the results from run to run.)
Many thanks.
3 votes -
Better experience for __SOURCE_DIRECTORY__ in F#
The FSharp compiler macro 'SOURCE_DIRECTORY' doesn't seem to behave as expected in linqpad - specifically it points to a linqpad temporary execution directory, and not where the .linq file itself resides.
This makes it problematic to use F# type providers within linqpad. Referring to data files relative to the script is pretty common, but the path supplied to a type provider has to be a compile-time literal - ie Util.CurrentQueryPath can't be used. Absolute paths obviously break across machines.
Not sure if a fix even is possible (I can't see anywhere on the F# compiler where you can…
0 votes -
Create a SQL view in the database directly from a Dump() result
Have the possibility to create a SQL view from the result of a dump() !
Linq is create to quickly extract complex data. If after you have just to click a button to save this in database it will very useful.1 vote -
Support multiple versions of a nuget package
Right now we have some linqpad scripts that use 1.7.1 of NEST Elasticsearch and some using 2.4.5. But we can not share those/use them on the same machine since there is only one 'NEST' directory under Linqpad\Nuget, right?
Not sure how this would be handled since you want to upgrade etc, but maybe the diretory should contain the version number in it? Then you could in theory have 2 versions downloaded.
1 vote -
being able to save a user work context
I usualy work by batches... at one client I use thoses queries, while at this other one, I use a different set...
And I have like 10-20 queries open, in a specific work context...
Context switching is a bit of a nightmare....
If only I had a button to save not the files themselves, but the specific work context, I could just reopen a previous context and off I'm gone...
1 vote -
Heatmap (profiling)
I guess it would be rather simple to change the background color per line, based on how much time the code spends. ..
So, when running the LinqPad script, we already have a pointer in the left side that shows what is running. By simply logging the time each line spends, it would be possible to color the background or some indicator in the linecounter-area which shows heavy sections.
This feature should be an alternate "Run" button, looking like a stopwatch.
After the script has completed (or while executing) each line is decorated with a color that indicate how much…
2 votes -
Dump should output script line number
In scripts with multiple calls to Dump, it is sometimes difficult to resolve Dump output with the specific Dump call that generated that output. If the Dump output contained the line number that originated that output, it would help in this regard.
6 votes -
Add an index row number column
The very left column (for selecting rows) should be a rownumberer column. Showing the index number of that row. Handy if you are sorting by a particular column and then want to quickly see how many are in each group.
1 vote -
show me the syntax tree even when a compiler error occured
now when a compiler occured, you got nothing in the screen.
no results, no syntax tree, only error info.
there are three kind of compiler error, lexer error, grammar error, semantic error.
if the error is semantic error, the syntax tree must have been generated, so i wish it could be shown in the screen.or in a nutshell, show me the syntax tree when it is possible.
i want this feature for debugging compiler. XD
1 vote -
Show the JIT assembly code like Visual Studio's Disassembly window
Sometimes rather than viewing IL I want to see the exact assembly code the JIT produces on my computer. LINQPad is a perfect place for such a playground.
22 votes -
allow extensions that act on the linqpad editor itself
It would be cool if you could write extensions or plugins for LinqPad which act specifically on your LinqPad selection or clipboard. Then configure shortcuts to call them.
Some examples:
Uppercase or Lowercase current selection.
Take current clipboard input and format it before pasting it into the LinqPad text editor view.
etc...
9 votes
- Don't see your idea?