1205 results found

1. Show more file types in the My Queries tab

   By default, LINQPad seems can only shown *.linq, *.json, *.csv and *.txt files in a folder. I'd like to show more file types especially some other text file types such as *.md.

   1 vote

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

2. Gather and visualize DOTNET_Jit* dumps.

   Allow user to switch on gathering of JIT dumps (DOTNET_JitDump and rest) and visualize and/or save them.
   Provide UI (or at least suggestions/help) for building filter patterns.

   3 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

3. Allow users to add UI scripts as menu options

   It would allow users to include interactive scripts in a dropdown menu, similar to the interactive regex utility. Clicking on a script would run it in the background, and the result area would automatically maximize, displaying interactive controls.

   1 vote

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

4. Excel File Integration with Intelligent Structure Recognition

   I frequently utilize Linqpad for processing Excel files by reading data through the FileInto method. My workflow typically involves manipulating this data and subsequently storing it in a database. To streamline this process, I propose an enhancement to the user experience with the following capabilities:

   Keyboard Shortcut for File Selection: Implement a shortcut key that prompts the user to select an Excel file. This would enable quick and direct access to data files without navigating through menus.

   Automatic Structure Discovery: Upon file selection, Linqpad could automatically analyze and ascertain the basic structure of the Excel file. This functionality should include:

   Detection of columns and rows
   Identification of data types within cells
   Recognition of table names and ranges
   Intellisense Integration: Leverage the discovered structure to enrich the Intellisense feature. This would allow users to:

   Autocomplete column and row references
   Preview data types and values on hover
   Navigate through tables and ranges efficiently
   By incorporating these features, users would benefit from a more intuitive and efficient way to interact with Excel files within Linqpad, greatly enhancing productivity for database-related tasks.

   Sample code
   FileInfo fi = new FileInfo(@"D:\DataFiles\data.xlsx");
   using (ExcelPackage excelPackage = new ExcelPackage(fi))
   {
   ExcelWorksheet data = excelPackage.Workbook.Worksheets[0];
   var start = data.Dimension.Start;
   var end = data.Dimension.End;
   for (int row = start.Row + 1; row <= end.Row; row++)
   {
   var column1 = data.Cells[row, 1].Text.Trim();
   // do something
   }

   I frequently utilize Linqpad for processing Excel files by reading data through the FileInto method. My workflow typically involves manipulating this data and subsequently storing it in a database. To streamline this process, I propose an enhancement to the user experience with the following capabilities:

   Keyboard Shortcut for File Selection: Implement a shortcut key that prompts the user to select an Excel file. This would enable quick and direct access to data files without navigating through menus.

   Automatic Structure Discovery: Upon file selection, Linqpad could automatically analyze and ascertain the basic structure of the Excel file. This functionality should include:

   … more

   3 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

5. Add support for HierarchyId

   Please add support for HierarchyId, I was expecting this to be available in LINQpad 8, as it was included in the latest version of EF Core.

   1 vote

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

6. linqpad8 open in excel file name append random

   linqpad8 open in excel file name append random

   0 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

7. Add an option to disable auto-recovery

   Sometimes scripts can contain information that you do not want to be saved to disk. You write the script with a placeholder for that information and then when you come to use it later you overwrite the placeholder, run the script and close it without saving... except it turns out that LINQPad 7's auto-recovery is saving copies of the sensitive information to disk every 10 seconds. If you're running from an SSD then its wear-levelling mechanism makes it tricky to remove that information from the SSD, simply overwriting and then deleting the file is not enough.

   I know that LINQPad offers mechanisms for storing passwords but they can be overkill and you are relying on DPAPI securing those passwords properly. I also know that the sensitive information is in RAM - I can live with that. I just don't want it on disk.

   It's not the most important thing in the world, LINQPad 5 does not write auto-recovery files so it can be used for these kinds of scripts, but it would be nice if LINQPad 7 could be used as well at some point in the future. Perhaps a boolean in the advanced settings that controls whether auto-recovery is enabled or not?

   Sometimes scripts can contain information that you do not want to be saved to disk. You write the script with a placeholder for that information and then when you come to use it later you overwrite the placeholder, run the script and close it without saving... except it turns out that LINQPad 7's auto-recovery is saving copies of the sensitive information to disk every 10 seconds. If you're running from an SSD then its wear-levelling mechanism makes it tricky to remove that information from the SSD, simply overwriting and then deleting the file is not enough.

   I know that LINQPad… more

   1 vote

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

8. Use a Newer File Type When Exporting to Excel

   Currently, LINQPad v5 and v7 both use the "Web Pages and Excel 2003 XML Spreadsheets" file type (format) when exporting data to Excel from the LINQPad Results pane. Under non-regulated conditions, it is possible to open Excel's Trust Center and authorize the "Web Pages and Excel 2003 XML Spreadsheets" file type (Trust Center -> File Block Settings). However... many companies must abide by security posturing in today's environment. As such, security policy auditors such as Tenable have identified that this file type format should be BLOCKED from opening in Excel (https://www.tenable.com/audits/items/CIS_Microsoft_Office_Excel_2016_v1.0.1.audit:29268ad4a1c7bb369b13db79d95af0ef). Unfortunately (or fortunately, however you look at it), many corporations are REQUIRED to implement standard policies such as this.

   Needless to say, we are such a corporation and Excel is blocked from opening this file type. Because of this, when exporting to Excel from LINQPad, you may or may not get an Excel error/info box pop up telling you that the file type is blocked and how to manually edit Trust Center to allow. Often, the box does not appear and you are left wondering why LINQPad is "hung" and the only work around (if you can't click "OK" to clear the Excel info box) is to manually kill LINQPad using Task Manager (or, if you understand the issue, you can hunt for the process from Excel in Task Manager, kill it, and LINQPad will resume and in doing so, LINQPad pops up its own error reporting "crash" box identifying that a System.Reflection.TargetInvocationException has been thrown).

   Would sure love to provide amplifying screenshots, but can't do that here in this "post your idea" feature.

   Regardless... cybersecurity threat vectors are constantly evolving and for security reasons, as holes or implications are found, they must be closed. If LINQPad continues to use communication vectors (i.e. with Excel) that are no longer viable from a security standpoint, we'll suffer loss of LINQPad functionality.

   Respectfully request that LINQPad use a more modern file type (format) when exporting to Excel. Thank you.

   Currently, LINQPad v5 and v7 both use the "Web Pages and Excel 2003 XML Spreadsheets" file type (format) when exporting data to Excel from the LINQPad Results pane. Under non-regulated conditions, it is possible to open Excel's Trust Center and authorize the "Web Pages and Excel 2003 XML Spreadsheets" file type (Trust Center -> File Block Settings). However... many companies must abide by security posturing in today's environment. As such, security policy auditors such as Tenable have identified that this file type format should be BLOCKED from opening in Excel (https://www.tenable.com/audits/items/CIS_Microsoft_Office_Excel_2016_v1.0.1.audit:29268ad4a1c7bb369b13db79d95af0ef). Unfortunately (or fortunately, however you look at… more

   1 vote

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

9. OnInit functionality for F#

   The void OnInit() hook, used for for example starting Avalonia before running and dumping UI elements, does not work for F# (Or, rather, I struggle to figure out how).

   The twitter discussion on Avalonia and F# with some creenshots are here https://twitter.com/bjartnes/status/1717422836250271800

   It would be nice with a feature similar to the OnInit hooks but for F#.

   3 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

10. Close AI Assistant Settings Window Also Closes Preferences

    When I close the AI Assistant Settings window, I except to be returned to the main Preferences window. Instead, both are closed. Is this a bug?

    3 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

11. make SQL output so I can run it in SSMS

    in the SQL output window instead - the parameters emitted as coments are not executable.
    Putting them on separate lines with a declare in-front and the appropriate type in-front would be very useful

    e.g. instead of

    -- Region Parameters
    -- @year_0='2024' (DbType = Int16), @period_1='5' (DbType = Int16)
    -- EndRegion

    output:

    -- Region Parameters
    -- declare @year_0 int ='2024' -- (DbType = Int16)
    -- declare @period_1 int ='5' -- (DbType = Int16)
    -- EndRegion

    3 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

12. Improve debugging text variables

    LINQPad is currently very not great at debugging anything with text.
    - There is no way to set line endings to Unix vs. Windows
    - When I paste text with Unix line endings, LINQPad silently modifies my strings to use Windows newlines. Boo!
    - There is no way to see line endings, because they are not shown in the debugger, even with "dump", so when writing string parsing code, my counts are just mysteriously off, more with every line.
    - The debugger "VALUES" column uses a variable-width font, so it is hard to compare values at a glance because even those with the same number of characters have very different widths
    - Even if using Windows newlines, "dump" loses the ending newline

    My suggestion is:
    - Show line endings, especially with "dump" which by name I would expect would show me the exactly contents of my variable
    - Use a fixed width font when showing values
    - Enable a change of line endings. Rider makes this a small button in the extreme lower-right of the screen which shows the current endings, e.g. "CR", and allows you to change them to CR-LF and back.

    LINQPad is currently very not great at debugging anything with text.
    - There is no way to set line endings to Unix vs. Windows
    - When I paste text with Unix line endings, LINQPad silently modifies my strings to use Windows newlines. Boo!
    - There is no way to see line endings, because they are not shown in the debugger, even with "dump", so when writing string parsing code, my counts are just mysteriously off, more with every line.
    - The debugger "VALUES" column uses a variable-width font, so it is hard to compare values at a glance because even… more

    4 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

13. REST client using .http files akin to whats been added via https://learn.microsoft.com/en-us/aspnet/core/test/http-files?view=aspnetcore-8.0

    Would be great to add in support for .http/.rest files the same as they've done for VS and VS Code
    This would help make LinqPad a great playground for producing and consuming data going through rest services for test and development

    7 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

14. Support custom keymps and text editing actions like vscode

    Would be nice to have custom keymaps like the vscode one.
    And actions like ctrl+D in vscode, move line up, down, delete line, copy line.

    2 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

15. manage users attached to the 10 User license from central location

    I can partially see the machines that are connected to my license but would like to be able to see it by user name, since it is a 10 user license. Would be nice to manage what users get the license and delete users and machines if someone leaves.

    3 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

16. Jumping to #load file should consider preceding #load(s)

    If my file contains multiple loads

    load "filea.cs"

    load "fileb.cs"

    Then, if I jump to fileb.cs, then types from filea.cs should be available when viewing fileb.cs.
    This without adding #load statements to fileb.cs, of course. The viewing of fileb.cs should somehow be in context of myquery.linq.
    Allowing strongly typed intellisense edits and F5 still running the main method from myquery.linq.

    1 vote

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

17. Exit

    Option to hard exit the query on finish.
    From my understanding there is no such option today.

    The only option is to exit the current query when a new one starts. Ex. "Util.NewProcess" or "Always use Fresh Process per Execution".

    The problem I get is that if I have a "unstoppable" background worker, this will still be running in the background until I start a new query.

    The workaround is to use a "try/finally" with a "Environment.Exit(0);" , however this seems hackish. Also tried "Util.KeepRunning" but that did not help.

    This is a big issue if more than one query is run in parallel, processing against the same database or similar. Then only one of them will be killed on re-execution of the query.

    Option to hard exit the query on finish.
    From my understanding there is no such option today.

    The only option is to exit the current query when a new one starts. Ex. "Util.NewProcess" or "Always use Fresh Process per Execution".

    The problem I get is that if I have a "unstoppable" background worker, this will still be running in the background until I start a new query.

    The workaround is to use a "try/finally" with a "Environment.Exit(0);" , however this seems hackish. Also tried "Util.KeepRunning" but that did not help.

    This is a big issue if more than one query… more

    1 vote

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

18. Add multilingual support for LinqPad

    for example Chinese, Japanese, Russian, etc. to improve the efficiency of non-native English developers. Although LinqPad words is not cumbersome, but I think this should be a basic function.

    3 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

19. Cache object DateOnly TimeOnly

    I got unhandled exception when cache object has DateOnly and TimeOnly property

    3 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

20. Port LINQPad to Avalonia XPF for Mac/Linux users

    The Avalonia team recently released a cross platform version of WPF, called XPF. It’s my understanding that WPF is what powers LINQPad and is a key problem holding it back from being cross platform.

    Is this a feasible solution or something that could be considered? Would absolutely love it if I could keep using LINQPad on my Mac

    3 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close