236 results found
-
Add Entity Framework support for Code First
The Entity Framework support currently requires the different xml files; EF will support Code First (currently in features CTP 3) which is all code, no xml files. It would be great to have LINQPad allow for EF Contexts using Code First.
75 votesLINQPad now supports both standard and code-first models.
-
Show compiler warnings
Would be nice to see warnings like we do errors
14 votesDone: Compiler warnings are displayed from version 4.31.3.
-
Add support for output parameters for stored procedures
Some way to extract values from output parameters like:
int outValue;
int inValue = 100;
stored_procedure(inValue, out outValue);9 votesSee “What’sNew” for info on how this works.
-
make more options
If you are going to release thjis beta version of LP4 then please please please give us the option to turn off the auto lambda stuff. Most of the time when I do blah.Count() in LP I just want the count, I don't want to include a lambda. Same with many of the other extension methods. It gets in the way ALL the time!
7 votesYou can switch this off as of v2.22.1. Note that you also work around this by pressing Space, Enter or ( instead of tab. Pressing Space or ( is actually better anyway, as it saves a keystroke.
-
Allow the keyword "using" on the Additional Namespace Imports tab of Query Properties
Sometimes it is easiest to copy and paste using directives from source code. However, if I paste the following:
using System;I get the following error:
Identifier expected; 'using' is a keyword15 votesAvailable in 4.37.1
-
Cache executed LINQ commands
When a LINQ query is executed, it appears LINQPad compiles and executes the expression each time. If the query is executed a second time without any modification, the full performance hit of the recompile still occurs. Caching the compiled LINQ would improve performance significantly; the cache value could be invalidated if the query changed.
3 votesCompleted in 4.36
-
enhance intellisense
Intellisense should popup when writing, not only when CTRL+Space'ing
just like Visual Studio.
1 vote -
At least allow changing of the editor windows background color? (pure white bothers my eyes)
While I don't expect to allow changing of all of the code coloring elements, at least just allowing the change of the background color of the editor window would be nice (I prefer a slightly off-tan color for example)
4 votesYou can set the editor background color from v2.22.1 in Edit | Preferences. I’ve also tweaked the text color set for dark backgrounds – let me know your thoughts.
-
BUG: Clone Query, Query Properties are duplicated
I have some default namespace imports set up.
When I use the "Clone Query" feature, then check the new query's "Query Properties", the namespaces are listed twice.3 votes -
Allow tabs to be renamed (without saving)
Instead of a new tabs always being named "Query n", allow the tab to be renamed without saving it to a file first. I think it would also make sense to not allow renaming of a tab from a file that was loaded.
21 votesThis feature is now available in LINQPad 6. Use the context menu option, or press Shift+F2.
-
Tuple support
Support Tuples - probably necessary to effectively keep-up with VS2010
3 votesDownload LINQPad 4.x
-
Integrate web query sharing
Would be cool if we could share queries to frineds through instant messaging in a similar way that Small Basic does it:
http://blogs.msdn.com/smallbasic/
it will store the query on a server somewhere and give a short link you can hand out for people to use.23 votesDone! File | Upload to instant share.
-
Collapsible Regions
I use SSMS quite a lot for queries that I use often. One missing feature in SSMS is collapsible regions, but there is a plugin for doing that. This has made canned queries that I use often more easy. It would be nice to have something like that in LinqPad. It would be handy to be able for instance to create canned queries that have a few variables at the top and a region of query code that is collapsed so that it is easier to look at and harder to mess up the code by accident.
3 votesThe latest build allows regions in ‘Program’ mode.
-
9 votes
Completed in latest build
-
provide AnyCPU version of LINQPAD (as in the past)
The new version is only x86 (which of course can be handy sometimes on a x64 OS, so please provide both)
18 votesDone. Go to www.linqpad.net/beta.aspx
-
Make system tables accessible
If there is a way to access the system tables, I've missed it.
Would be a useful feature though.
6 votes -
2010-style Intellisense (match in-string instead of just start-of-string)
I deal with legacy databases where the table and column names often have common prefixes (imagine a Products table with columns named productcolid, productcolname, etc, just as an example). This means I have to get past said prefix before intellisense can start differentiating.
A better approach (at least as an alternative) is what VS 2010 introduces where it filters based on matching the string-so-far. This has made a huge difference when using VS 2010 and linq-to-sql / linq-to-EF and dealing with these databases.
ScottGu has a good post detailing with it - specifically check the "Code…
6 votesCompleted in latest build!
-
Add support for InternalsVisibleTo
Sometimes I want to create my Entity Framework model as internal, but also use it from LINQPad. It would be good if there was a way to do this without having to change all model items from internal to public, and then back again when I want to release my assembly.
12 votesAvailable from v4.44.4. Add [assembly:InternalsVisibleTo(“LINQPadQuery”)] in your assembly and enable the option in LINQPad’s preferences.
-
Ability to post clickable links in results
Maybe by having some kind of escape code whereby your dumped string doesn't get encoded or by having tags like in forums [url][/url]
2 votesThis has just been implemented in the latest version – see Peter’s comment
-
Support ADO.Net providers that contain EF implementations
ADO.Net is a provider model (factories). You can load and query the provider to see if it supports EF. That is the whole point of having ADO.Net as a provider. Adding each provider one at a time means a lot of hand coding per provider. It would seem to be a better use of your time to just support ADO.Net and the provider model.
This would allow you to use VistaDB, Sqlite, Oracle, MySql, etc as long as they have an EF provider that supports the provider factory correctly.
3 votesYou can specify any provider and connection string from V2. Please note that this only works with static DataContexts – i.e., EDMs that you’ve defined yourself in VS. It’s not possible to do otherwise AFAIK there’s no general and reliable way to query schema via EF and ADO.NET.
- Don't see your idea?