1205 results found
-
Allow viewing entire byte[] buffer contents
Linqpad does a nice job of rendering byte[] buffers (as hex), but truncates the display after like 20 bytes or so.
I'd be nice if when it did this the display was hyperlinked so you could click on the 'byte[]' and get a popup with the full* buffer displayed.
(I need to compare bytes-on-the-wire with what the application did/didn't manage to parse, and hacking this kind of popup in the query itself is painful)
- within reason. First few kb would be enough in most cases.
1 vote -
Have a version of LINQPad with a notebook UI ala IPythonNotebook
I'd really love a version of LINQPad along the lines of IPythonNotebook or Mathematica. Ideally it would be hosted in the cloud. I'd use such a thing from every one of my computers all day every day and would happily pay a monthly subscription for the privilege.
6 votes -
Option to skip generating SQL etc. when running long running queries?
I'm guessing this would increase speed a lot?
0 votes -
Tooltip balloon duration
When I examine the IL view of my code, I often hover over the OpCode instruction to read the description. The tooltip will show for a few seconds and then fades outs.
I would like to increase the duration of the tooltip balloon or disable the fading.
2 votes -
Save Query Custom Settings
I would like the ability to save "settings" in the query. For example, if ask to select a file, I would like to save the file that was selected for the next time I run the query. This would be perfect if I could save the data inside the query file XML section.
3 votes -
Allow option to prompt before executing production queries.
I love that you allow users to flag production connections and you make it visually obvious when a production database is being used.
A configurable option (even if the default is off) to present the user with a simple "OK"/"Abort" confirmation dialog before executing a query against a production database could serve to save users from terrible mistakes. I am very grateful that I myself have not made this mistake, but it would be a very easy thing to do that could be avoided with a couple of lines of validation.
One could recommend that query authors write this into…
2 votes -
BUG: Custom Context Driver is locked until closing linqpad
I'm building a Context Driver for a relational database and the documentation says to edit the DevDeploy.Bat file to copy the binaries to the context folder. Two things, one is that the documentation needs to get updated to reflect the new "per user" folder location as well as the "Framework 4.6" folder. And lastly (but more importantly) Visual Studio will fail to build because the bat file exits with error code 4. I close LINQPad and I can than build properly.
2 votes -
Fix clicking on explorer item hyperlink navigation
I'm making a Context Driver for a DB2 relational database, and I found that setting the ExplorerItem.Hyperlink makes the appropriate item (Column) look like a hyperlink. If I click on it nothing happens. If I expand the referenced ExplorerItem's Parent (table) then scroll back up and click on hyperlink it works as expected.
1 vote -
AutoComplete object type filtering (Similar to ReSharper)
Like many others, I've grown to love certain features of ReSharper. One such feature is the ability to filter the AutoCompletion list by object type using keyboard shortcuts or by clicking on the icon of the object type (such as namespace, class, interface, property, field, etc.). I think that this would be a really nice addition to LINQPad.
3 votes -
Give each query a unique ID
I currently have a support assembly I use to make queries more dynamic (e.g. asking for input) and I save the history in a file. To organize the history I use the query path, but sometimes the query gets moved. I would like to have a unique query ID for every query created (i.e. GUID?)
2 votes -
Quick search/open/edit by name views/stored procedures/functions
In database with lot of views/procedures/functions is hard to find the desired object for editing just looking in the tree view.
Would be great if LinqPad have a menu item/shortcut opening a dialog for typing and searching incrementally the object and openning it after found.2 votes -
Very dissapointed
Jus t purchased the product and was expecting autocomplete to work in SQL as well as everything else. The whole reason for making the purchase. I see I have 30 days to play with it and ask for a refund which I'm pretty sure I will do.
4 votes -
tab focus
After closing a tab the next tab to get focus should be in order of most recently used.
3 votes -
query designer
create something similar to the sql server query designer.
1 vote -
20 votes
-
Support foreign key columns ending with "Fk" instead of "ID"
Currently entity navigation is optimized for table columns ending with the suffix "ID", for example a CustomerID will get a navigable "Customer" field created.
In a database where the pattern is like CustomerFk, the navigable field would be named CustomerFkEntity, which is painful to write each time in queries.
Please allow a more permissive foreign key naming detection or allow it to be configurable.
3 votes -
Add refresh snippets command
add a command to refresh snippets to save having to close and reopen LINQPad when editing snippets.
1 vote -
Is there a way to implement OWIN ApplicationUserManager
public class ApplicationUserManager : UserManager<ApplicationUser>
{
}gives the followin error: The type 'UserQuery.ApplicationUser' cannot be used as type parameter 'TUser' in the generic type or method 'Microsoft.AspNet.Identity.UserManager<TUser>'. There is no implicit reference conversion from 'UserQuery.ApplicationUser' to 'Microsoft.AspNet.Identity.IUser<string>'.
Is there a way to resolve that?
4 votes -
BUG: automatic intellisense occuring on single letters
When typing something like
.Where(x => ....)
pressing space after the x fills in the intellisense menu choice which pops up automatically.4 votes -
Autocomplete should suggest overloadable members
AutoComplete is very handy. It helps with discoverability of all libraries in use. Visual Studio was smart in where it could suggest things, depending on the context. However LINQPad, while close, is lacking in some areas. In particular, overloadable members of a class.
When within a class and you type overload, LINQPad should list all members of the class that can be overloaded. When a member is selected, it should spit out a default implementation (to call the base implementation). If an overloadable member is implemented, it should not be listed.
Please make it so.
2 votes
- Don't see your idea?