1192 results found
-
Additional mouse selection support
Add additional support for selecting text with the mouse that works the same as most Windows applications:
In query editor pane:
- Triple-click = select entire line
- Triple-click + drag = select multiple entire lines
In SQL results view pane:
- Double-click = select entire word
- Double-click + drag = select multiple entire words
- Triple-click = select entire cell contents
11 votes -
Create DataContext with XmlMappingSource
In the connection properties dialog, you could add a field for XmlMappingSource path and then use it to create the DataContext:
string xml = File.ReadAllText(pathToXmlMappingFile);
MappingSource mapping = XmlMappingSource.FromXml(xml);
DataContext context = new DataContext(connectionString, mapping);
10 votes -
10 votes
-
Tables node under database tree
Add Tables node and display all database tables under this node. Like you do in Views, Stored Procedures, and Functions.
Currently all tables are displayed as direct children of the database node.
10 votes -
encoding
To Allow set text encoding for result. Now LinqPad can get result , but it is unreadable to me since what I have in result is not English. Thanks!
10 votes -
Instance share should include My Extensions
I shared a script with a colleague today. However we realised it would not run because I was using and referencing logic from the My Extensions script.
My idea is that when a script is uploaded to instance share, it should include (or allow me include) logic from the My Extensions script, so that the script is able to be run on another machine without modification
10 votes -
Implement a driver based on the famous dapper library from Stackoverflow
Implement a driver based on the famous dapper library from Stackoverflow. Dapper is faster than Linq2SQL or EF. It'd great to take advantage of it in LINQpad.
10 votes -
Adding PowerShell support
It would be nice to be able to test PowerShell From LINQPad, currently I have to use PowerGUI for testing Powershell Script.
10 votes -
Support Touch Interactions in the Code Editor
Many of the tool panes in Linqpad already support touch scrolling. This makes it very comfortable to use on a touch enabled device like a Surface. However the Code Editor does not support touch scrolling. Visual Studio recently introduced this feature and it is great for reading code on a tablet.
Please support this in the Linqpad editor also.
10 votes -
Add Connections using Data Context from a NuGet Package
It would be great to be able to package up custom DbContext assemblies and app.configs (e.g. dev, uat, prod) in a NuGet package then reference the package from the "Add Connection" dialog.
10 votes -
Copy to CSV or similar
I can effectively do this using export to Excel and then select all / copy. But I do a lot of statistical analysis and need to copy data results to and from other programs. They support importing from the clipboard, but the clipboard text must be comma or tab separated (or even fixed--parsable in a line-per-row fashion--i.e., not markup).
It would also be nice if you could suppress the summary line.
9 votes -
linq2xml
It would be nice to be able to load, query and update xml files.
9 votes -
Add ability to customize the table context menu in the schema tree
The table context menu items in v4.37 are much improved especially adding the 'Explore top 100 …' - Thanks you!
But I would like the ability to add extra menu items for example to run a custom visualizer or perhaps a different query template to the ones provided.
9 votes -
Integrate with GitHub (gist)
Many LINQPad scripts are short blocks of code that would be useful to a wider community if shared.
Sharing a LINQ 'script' as a Gist on GitHub means you get versioning/change management and social sharing. You can get the top LINQ 'scripts' written by others and share your own. Others can comment on your scripts / fork them etc.
Perhaps it could be implemented as another "Tab" next to "My Queries" and Samples, called "My Gists".
9 votes -
autocomplete data-entry on "Additional Namespace Imports" tab using info from the assemblies on the "Additional References" tab.
Typing namespaces is error prone and not validated on the Additional-Namespace-Imports tab. In loading the the "Additional References" assemblies, the namespaces (including spelling and character-casing) could be auto-completed to their correct values. I forgot the case of one character in the namespace, and my only clue was that intellisense wasn't picking up the classes that I expected in the namespace I had mistyped.
9 votes -
Allow users to disable highlighted text execution
If I attempt to run a query with anything highlighted only the highlighted text is executed. This is a really nice feature for some scenarios but I'd really like the ability to turn it off.
When I'm building longer code queries i almost always have code highlighted inadvertently so I am constantly accidentally executing a few lines of code. This is usually just annoying but it has a huge potential to be dangerous as well as it lets me accidentally bypass my other conditions when doing data operations.
9 votes -
Support EF derived entity types in the schema tree
If one has derived entity types defined in the model and doesn’t use MEST (default scenario), the derived entities are not shown in the schema tree, since only entity sets defined in the model are currently shown. Per default it means only base entity types. It makes model exploration capability very limited. Consider a model where all the entities derive from a single base type MyObject (arguable but viable design). Then you end up with only one “table” entry MyObjects in the schema tree with few to none properties defined. All the hundreds of “real” types with all their valuable…
9 votes -
Support F# under Visual Studio 2012/Windows 8
Currently, latest release looks for fsc.exe in C:\Program Files (x86)\Microsoft F#\v4.0\, but under VS 2012 on Win8, it's actually under C:\Program Files (x86)\Microsoft SDKs\F#\3.0\Framework\v4.0\
9 votes -
Map char(1) to string, as sqlmetal does
When I generate a DataContext through sqlmetal, it converts all char fields to strings. Not what I'd expect it to do, but not a bad idea.
When I generate my entities through LinqPad, char fields are left as char, making my sqlmetal generated code incompatible with LinqPad.Just as there are options on pluralizing and capitalisation, It would be useful to have a "convert char to string" option as well.
9 votes -
Export Query Option
I have been using LinqPad for a while and have created a lot of extensions and other helpful utilities in My Extensions. When I go to share a LinqPad query with someone else, I forget that I am using my extensions and so they cannot compile or run it.
It would be great if there was an "Export Query" function that would detect calls into "My Extensions" and copy applicable (or all) code to the bottom of the query (query would have to be forced to C# Program Mode). Then the query would be ready to send to someone else,…
9 votes
- Don't see your idea?