1205 results found
-
"Add Folder" option to Additional References menu
Some NuGet packages load native assemblies at run-time that are expected to be in a specific folder relative to the root folder. This makes LINQpad incompatible with these packages as LINQpad does not maintain the folder structure.
Having the ability to explicitly add a folder rather than a file to a query will allow you to maintain the folder structure the NuGet package expects.
Ex. https://github.com/charlesw/tesseract/issues/484
I also had to implement a similar workaround to use some methods in the ML.NET libraries (tensorflow related).3 votes -
Debug over all grouped tabs with F11
If possible allow group tabs to a debugginggroup. Then allow to singlestep "F11" debug over all tabs in this group.
3 votes -
Disable Automatic Update when the update would deregister the product
Don't automatically update and relaunch from a registered product to a newer version we don't have the license for.
I appreciate the product but this is an appalling show-stopping bug guys.
I've disabled automatic updates for 9001 days to "temporarily" fix the problem but I shouldn't have to do this.
3 votes -
Allow exporting dump window programmatically.
Rather than explicitly writing to a log file, I often just export the dump window after running a query.
I have not found a way to programmatically create this export - something like
Util.ExportDump(filename, ExportFormat.Html).
3 votes -
IL output could show storage too
Comparing the IL C#1 view to ILSpy, the one thing (other than font) that makes it easier to understand in ILSpy is that it includes output for the fields storage, e.g. the IL C#1 for the expression
await Console.In.ReadLineAsync()
generates a MoveNext that refers to fields we can't see the definition for in LinqPad but can see in ILSpy.3 votes -
util's saved string browser
Utils.SaveString is awesome, but would be nice to have some kind of viewer/browser to see what is being stored
3 votes -
Autocomplete classes in any namespace (+ add using if needed)
Hi, I would like to be able to complete any type that is not in the current using namespaces, similar to what Rider does. It is very inconvenient otherwise.
Example:
Suppose I want to use aRNGCryptoServiceProvider
class, but I don't know what namespace it's in or how it's exactly spelled. I only remember it contains Crypto in it. So I would type "Crypto", press CTRL+Space and get it in the completion list, even though its namespace was not in the using list. You can show its namespace in a completion item to the right, likeRNGCryptoServiceProvider (in System.Security.Cryptography)
.…3 votes -
Option to disable NuGet/EULA prompts
I would like an option to disable all NuGet related prompts. I would like to be able to run a script without having to worry about NuGet package download confirmation or any particular license attached to the NuGet package. I find these annoying since I use packages from a private feed.
3 votes -
Convert to class from anonymous objects
Something like in VS 2019, right click menu, "Convert to class". It would be so helpful for tasks like data exploration.
3 votes -
Support custom project properties and environment variables
Sometimes we need to specify custom project properties and environment variables for a query, for example,
<EnablePreviewFeatures>true</EnablePreviewFeatures>
and env varsDOTNET_TieredPgo=1
. Please allow us to customize project properties and environment variables.3 votes -
Dark Theme like Windows 10 Dark / Visual Studio 2019 Dark
Dark Theme like Visual Studio 2019 Dark
3 votes -
Add support for C# 9.0 in LinqPad 5
I have both LP5 and LP6, but I don't seem to have a way to write code snippets in C# 9.0 against .NET Framework 4.6/4.7/4.8. I'm fine with switching over to LP6 if/when I want to target .Net core or .Net 5/6, but I still need a way to test the latest language features against the older Framework versions.
3 votes -
Require auth like fingerprint/windows hello for production connections
Today we use read only connections for production databases and it works well. But everyone once in a while we do need to change a value in a production db.
Today we then connect with different credentials which takes a little time.My suggestion is a connection that linqpad enforces with fingerprint, windows hello or similar.
So the connection is always there (and read/write) but every time I want to use it I have to authenticate. This would still be much faster then creating new connection (and in the other scenario I also have to remember to disconnect manually but…3 votes -
3 votes
-
Add "jk" to escape in vi mode.
LINQPad only supports "kj" for now..
3 votes -
support .exe assembly references
I can add a reference to an assembly that's blah.exe but I can't consume types inside it. If I copy blah.exe to blah.dll everything's fine, but that would appear to be a dull and unnecessary (and forgettable) step.
If there's a valid reason why this can't be delivered then fine, I'll live with it, but - granted I know diddly-squat about LinqPad internals - it doesn't seem like it'd be hard to add.
3 votes -
Add a context menu command "Copy as new List<string>" to the grid context menu.
Similar to the RedGate SQL Prompt function "Copy as IN Clause".
To use this, you return results into the grid. Then select a range of values in one column and select "Copy as new List<string>" from the context menu. It then copies the C# code for creating a List<string> with those values to the clipboard. For example:
new List<string> {
"OMO-155165",
"PQJ-155177",
"ABI-155153",
"HCI-155167"
}3 votes -
Add a "Enable Word Wrap" toggle button on the toolbar
I'm switching Word Wrap flag very often. When there is a big string in the Editor, I have to switch between Enable Word Wrap and Disable Word Wrap. So it would be better providing Keyboard shortcuts (Ctrl-E-W) or have a button on the toolbar.
Screenshot: https://imgur.com/HhnA2lr
3 votes -
add extension methods Folded and Expanded for overiding initial folded/expanded state
add extension methods Folded and Expanded for overiding initial folded/expanded state ignoring depth level from Dump function for that member
3 votes -
Single LINQPad for both .net framework and .net
It will be useful if a single LINQPad can handle both .NET framework and .NET queries. It will result in less context switching when working on different kind of queries.
I know separation has benefits of doing less testing for .NET Framework version as it is more or less complete, but it is annoying to switch and now I need to keep track of queries separately.
3 votes
- Don't see your idea?