1201 results found
-
Let the autogenerated DataContext table classes use properties, not fields
When using Visual Studio to generate a DataContext, the table classes use properties for the columns. When LINQPad does it, it uses fields, not properties. This is bad, because it creates a (too) subtle difference between the 2 tools. Code that works in one, may not work in the other.
1 vote -
Provide Recently Used list for Find and Replace text
I would love to see the the "Find what" and "Replace with" text boxes turned into combo boxes that drop down to show recently used values. It would be particularly helpful when performing non-trivial regex searches.
1 vote -
When dragging column name from connection box into a SQL statement, don't highlight it. just put the cursor at the end + 1 space.
When dragging column name from connection box into a SQL statement, don't highlight it. just put the cursor at the end + 1 space.
1 vote -
Use dynamic (ExpandoObject) properties as column headers in output
I have a script that produces an array of dynamic objects whose properties are all identical. It would be nice to have the output formatted as a single table whose columns are the properties of the dynamic objects rather than a table with a single column, Items, with links in each row to the Key/Value pairs.
1 vote -
Support output to browsers
I want to suggest LINQPad can utilize SignalR to output results into browsers. That will useful for multiple monitor users.
1 vote -
Lowercase VB keywords option
Since VB is case-insensitive, all its keywords can be lowercase without affecting compilation. In Linqpad4, I use to type all my VB code in lowercase (it's somehow much more readable). Now with LP5, I get code completion and other nice stuff, but all my nice lowercase code gets put back in normal VB style. If it's not too much work, a "Lowercase VB keywords" option would be great.
1 vote -
Show a waiting icon during "Navigate To Query" search
Show a waiting icon in the "Go To..."(Navigate To Query)" popup window during long query text searches
1 vote -
Auto-Expand Data Grid columns
When I query and get Data Grid results back, the columns always come out fairly narrow. I have to then click on each column to read it. The Data Grid controller allows you to expand all columns so that all data is visible in each. This would be helpful to have
1 vote -
Let "Export to ..." default to the users Documents directory (or let it be configurable).
I've never yet wanted to export my results to my queries directory (or whereever it defaults to now). I don't get the current behaviour ... do people actually want this ?
1 vote -
Exclusive Results Window Per Query Tab - detached mode
Keep results window exclusive to each tab so that various tab results can be compared or referenced when needed. Let's say I want to see the results of a query as a reference to other query I'm working on another tab, the result window goes blank as it is linked to the current query which is blank since not executed yet. But I still want to see the previous query results that I detached earlier.
May be an option to PIN/LOCK the results window to the query tab exclusively so that other tab's execution results will create a new results…
1 vote -
Avoid DevArt assembly collisions with user query references
Not sure how viable this is, but I spent all day today trying to find the source of an assembly collision that prevented some code compiling in Linqpad, only to find that the stray version originated from Linqpad itself!
If possible, I suggest you avoid injecting Devart.Data / Devart.Data.Oracle assemblies into the query app domain if later versions of those assemblies are already being (directly) referenced by the query. Otherwise you create assembly binding issues for the compiler.
Failing that, Linqpad.config should probably have some binding redirects for DevArt.Data / DevArt.Data.Oracle
(Linqpad 4.55 references DevArt.Data.Oracle 7.9.333.0, my query references assemblies…
1 vote -
Allow remote execution of scripts with lprun
We use lprun with teamcitry to generate various statistics and post them to our wiki every week. However today it is not possible to execute these scripts with lprun, without first manually enter the credentials on the particular machine first.
Lprun should be able to execute remotely, without having to manually configure it on every machine. A really simple way, would be to let users disable encryption of the password. Another possibility, is to let users specify a certificate to use for encryption.
1 vote -
1 vote
-
GridView results should use full width of pane if needed, instead of ellipsissing cell values
Using grid view, the column widths are currently set for the minimum to handle the header text, often visually truncating cell values even if there is unused width available in the grid UI.
If nothing else, divide the available space by the available columns to compute a minimum initial column width. Even better would be if it takes the retrieved values into account and make narrow valued columns narrower.
1 vote -
Allow Results To Be Screen Captured To Image Hosting Service
Ability to right click on the results area to do a screen capture (image) of the result(s) to be taken and sent to a predefined image hosting site.
Then provide access the image URL in the clipboard in either raw html or in StackOverflow format.
[Title Here](http://{Image Hosting Addy to image})
1 vote -
Allow user names for results grids
Simpley allow the usr to rename the grids, or perhaps to provide a comment in the sql to name the results grid for each query when doing multiple queries.
1 vote -
Export to Visual Studio 2015 Snippet
Allow for LINQPad Query to be exported as a Visual Studio 2015 XML Snippet file.
1 vote -
Paste as comment
Paste as a comment block
Just like the paste as escaped string is great, i think paste as comment block would be just as useful.
1 vote -
have an option to display EntitySet counts
Display the count of EntitySet fields in the parent grid row, so that you don't have to click on them to see if they have any list members:
e.g.: | 1 | ivoice203 | CustName | InvoiceLineItemList (5) | 11/1/15 |
1 vote -
Bug - Intellisense does not working!
Intellisense does not working on big queries. I've an query with about 6.000 lines of code and intellisense does not working inside. On other (smaller) queries intellisense works fine. Using LP v5-03-03 beta Any CPU.
1 vote
- Don't see your idea?