1182 results found
-
Save As.. = Ctrl+Alt+S
New shortcut for "Save As" command.
4 votes -
Allow tree structure in editor to allow say #region and #define to be minimised similar to VS. Code could be hidden from users easily enough
Allow tree structure in editor to allow say #region and #define to be minimised similar to VS. Small scripts for users could be hidden from "users" easily enough using #region #endregion or if based on defind label around the whole thing
2 votes -
instant share should create a synced shared folder with all your shares in it
Currently if I instant share something, and want to make a small change, then I have to create new instant shares each time. Perhaps a simple solution is for linqpad to create a "shared" folder, inside that are files named according to the bitly styled instant share 38dHLx.linq etc. If I delete anything in that folder, then you (linqpad website) can delete the corresponding instant share, if I press control+u when inside a file thats an instant share, it should update? This will avoid linqpad having to create a whole web CRUD interface around "manging" my shares, or, reproducing GIST…
1 vote -
Add support for System.Console.Error.WriteLine
As of v4.45.05, calls to System.Console.Error.WriteLine appear to be silently ignored. It would be nice to see this output, ideally in a red font. This post linked below suggests using Util.Highlight("text").Dump(). Perhaps System.Console.Error.WriteLine could automatically map to this, much as System.Console.WriteLine automatically maps now. This would make LINQPad samples more portable.
5 votes -
Syntax alignment like visual studio
It would be handy to have "select" align underneath "from" like it does in visual studio. I often find myself tabbing code around to align it, but in visual studio its automatic alignment seems more natural.
1 vote -
Add scriptcs support
It would be great if LinqPad would support scriptcs or Roslyn since it already has NuGet support. Another option would be to export the .linq project as scriptcs project.
117 votes -
7 votes
-
Make "insert special" customisable
It would be cool to be able to add our own items in insert special (the top right of the data grid in premium), I suppose this is a super-feature of having a date picker
2 votes -
Date picker on data grid
It would be handy to have some sort of date picker and/or perhaps auto-insert of the current datetime in the data grid.
5 votes -
Adding New Connection defaults
Add a tab to the "Preferences" dialog for "New Connection Defaults". Allow the user to specify certain defaults for creating new connections. I often create a new connection (with the program defaults), then have to delete the connection and re-created to turn off "Pluralize EntitySet and Table properties" and "Capitalize property names". It would be nice if I could turn those off by default.
2 votes -
transpose output - same way as when using First() but for more rows
I have some tables with lot of columns, but only several rows, it would be nice to transpose the output to have SQL table column names on the left and SQL records (rows) in columns
Such transformation should be used, when some collection returns only one record (in nested table - Navigation property)6 votes -
Export multiline value from one cell in output into single excel cell
When exporting to excel table which has more lines value in one cell, linqpad splits the lines into separate cells and other "single line" values on the same row are merged into one. It would be nice to have multiline values also in one cell in excel.
24 votes -
A file-base "My Extensions"
If a special file in the same folder as the opened .linq-file exists (for example "_Extensions.linq"), it should be loaded and executed before the query executes. Extension: Search the parent directories too for this file.
16 votes -
sticky column headings in results view
I can see that there are sticky columns in the grid, but it was also be great to have them in the results view.
Perhaps when scrolling between different result sets it sticks to the current visible result set.
5 votes -
Reorder the parameters when using F1 key to search for documentation
The ability to search the documentation via google by pressing the F1 key is great, however the order of the terms is a bit different than titles in the MSDN docs.
For example, pressing F1 on the someType.Namespace queries the google for:
System Type.Namespace property
which doesn't yield expected results, however:
Type.Namespace property System
does. Should take less time to fix than it took me to write this :)
1 vote -
Autocomplete Linq-SQL basic methods
xx.InsertOnSubmit()
xx.DeleteOnSubmit()
SubmitChanges()and other basic LINQPad advertised as replacement for SQL Management for daily tasks should autocomplete even on the free version for users to get an idea of how well the autocomplete is working.
For example it could be enabled only on LINQ entities and that SubmitChanges(). All other objects should show no auto-complete and on manual autocomplete request an informative buy upgrade message.
3 votes -
Documentation generation
When you have long code in LinqPad (Several classes in one file) it is really helpful if we can have some documentation. However currently linqpad does not do anything in this area. As a start, it can generate the documentation skeleton when user type /// above the method, property etc. Then if that can be evolved to do the auto documentation generation from the method/property names (like GostDoc), that would be awesome!
6 votes -
Add "Export To Visual Studio" to generate a solution and project based on the LINQPad script
LINQPad is awesome for quick scripts, but sometimes they grow to the point that you just have to promote them to a full-blown Visual Studio project. It would be awesome to have a feature to be able to do a "Save As Solution", which would generate a Visual Studio compatible Solution and Project, and move your code into a new class as well as providing a generated DataContext.
50 votes -
Add OData as language
In this case i can use LinqPad as ODateClient, see nice result and can export the result to Excel ...
2 votes -
Export result to XML
It would be nice to export the result to xml. Two possibilities XML-Node and XML-Attribute. If the user chooses XML-Attribute one Data record is one XML node with all fields as Attribute, Nesting Levels are Nodes.
2 votes
- Don't see your idea?