1186 results found
-
Intercept and echo calls to Debug.WriteLine or other trace calls.
Adding a window that allows trace calls to be seen would aid in debugging drivers. These could be seen easily in LINQPad (perhap by enabling/disabling the visibility of these) when loading and testing a new driver or even allow such calls embedded in dynamically created source, to also log stuff - very hard to see otherwise.
6 votes -
Add support for Microsoft Portable Class Libraries
Portable Class Libraries helps developers write cross-platform libraries which can be very useful for things like DTOs, service/client code, extensions... etc
http://visualstudiogallery.msdn.microsoft.com/b0e0b5e9-e138-410b-ad10-00cb3caf4981
13 votes -
Convert URI to linq
I have a odata URI. I need a translation of it in Linq using linqpad. Is it possible?
1 vote -
Allow to change the "back-tick" key in the preferences (badly needed for non-US keyboards)
On keyboards without a back-tick key usable without any modifier key (alt, alt-gr), to select multiple columns you have to key-in <Alt>+<9><6>, which would already be pretty bad but actually gets worst on laptops without numerical keypads (a lot of them!): I have to key-in: <Fn>+<NumLock>,<Alt>+<9>,<6> for every column I want to select.
I own the premium edition, and don't use it because of this...
1 vote -
4 votes
-
Support a "refresh driver" feature to avoid the need to unload/relaod during development of a new driver.
In the Add Connection dialog is a 'Delete Driver' feature, I sugges you add a 'Refresh Driver' to that simply deletes the driver and reloads it again from the same place.
1 vote -
1 vote
-
1 vote
-
If user manually adjusts column widths in a query window - remember these settings.
If uses adjust the cols in a query result set, then if they run that query again and the result "shape" is the same, then use these adjusted col widths for these new results.
Only if the shape of the results changes from one run to the next is there any need to reset these (even in that case it could remember the widths I guess - on a per col basis)
4 votes -
Add PowerShell and autoComplete
Make Powershell a part of LinqPad. Make autocomplite for powershell and make suport for the lang.
15 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 -
1 vote
-
Add Ntlm authentication to WCF connections
It seems like you can connect using Ntlm to WCF
6 votes -
Add a help menu item provide code samples for how to use it's New Features. like "NEW Cache() extension method for caching results..."
Almost every week LinqPad give a new update verision. But as a user I don't know how to use these new feature, so these valueable feature can not make any value for me. I need some code samples show me how to use these new feature. So please add a help item under help menu to include code samples for new features and linq tips and .net tips...etc.
4 votes -
Include "My Extensions" file to "Search samples"
See the subject. The code within "My Extensions" seems to be not found by "Search samples..."
4 votes -
1 vote
-
Allow the user to sort using statements and references
Currently, it is very hard to find references on the "Additional References" and "Additional Namespace Imports" tabs when in the Query Properties window. This is harder when using LINQPad with enterprise applications that require a lot of references and using statements.
keep up the good work!
1 vote -
Allow "solution explorer" organization
It would be useful to organize a .linq file in multiple classes, exactly as in Visual Studio "Solution Explorer".
LINQPad is becaming a new light version of Visual Studio for me :).2 votes -
Allow .zip as a driver extentions
Allowing a driver to be named .zip would simplify testing and debugging of new drivers. LINQPad could allow this but warn the user when the driver is added "Warning driver should be named .lpx please contact driver vendor to get this resolved" or something. This will really ease the fiddling around at dev/debug stage.
1 vote -
Add a "throw driver exceptions" capability.
This capability would cause an exception to be thrown by a driver when it gets a serious error preventing executuion. A outer catch could cartch these and write them to a driver test output window along with stack data.
In addition when running LINQPad under debug the debugger could be configured to break when an exception is thrown - although there is limited src available - this would still allow a developer to see stack traces etc and gain insights into what might be wrong.
When this new feature is disabled LINQPad would behave as it does now.1 vote
- Don't see your idea?