1197 results found

1. Bug fix: prop <tab> <tab> shortcut only works on the first property of a class

   How to reproduce: New query, C# Program. Below Main() create a new class public class test. After the open {, type prop <tab>. You will see public int MyProperty { get; set; } as expected. Go the the end of the line and press return. On the new line, type prop <tab>. You will see PropertyAttributes in error. As a test, Visual Studio 2022 performs correctly. This shortcut is very helpful when adding many properties to a class.

   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…)
   1 comment  ·  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. Have an option for drop to clear current query text

   Suppose you start with a new query, then you can expand a database connection it will show you the tables and you can drag a table name into the current query window and it allows you to quickly run and see the contents of the table.

   But if you drag another table into the same query window it inserts the table name roughly where the drop occurs.

   It would be nice if there was a way of replacing the current text which would allow you to run the query and see the contents of that table.

   Perhaps this could be done if you hold down shift while dropping the table into the query window.

   This helps when you are looking through the various tables in an unfamiliar database.

   Alternative if there was a special way where you could generate a query that dumps every single table.

   Suppose you start with a new query, then you can expand a database connection it will show you the tables and you can drag a table name into the current query window and it allows you to quickly run and see the contents of the table.

   But if you drag another table into the same query window it inserts the table name roughly where the drop occurs.

   It would be nice if there was a way of replacing the current text which would allow you to run the query and see the contents of that table.

   Perhaps this could be… 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

3. Use a different application icon for 4.x versions
   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

4. Ctrl + E as alternative execute query shortcut

   It would be great if the Ctrl+E SSMS shortcut would be enabled as an alternative to F5. It's easier to reach and makes sense (E for Execute).

   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…)
   1 comment  ·  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. Provide more information about thrown exceptions (dump message, stack trace, etc).

   Provide more information about thrown exceptions (dump message, stack trace, etc).

   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…)
   2 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

6. Allow hitting Escape key to trigger 'cancel' like Shift-F5 does

   Since hitting Esc doesn't seem to trigger any other action, it would be useful for those of us with muscle memory to hit it when we accidentally ran something we shouldn't have. Much faster/simpler than the 2-key combo of Shift-F5. :)

   I'm not trying to ask for the larger-scope 'allow remapping keyboard shortcuts', just the Escape key. :)

   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. Update the static driver sample code to detect Context properties of type IEnumerable<T>.

   The UniversalStaticDriver class does not detect the properties of the customType parameter that are directly of type IEnumerable<T>. If the customType inherits IEnumerable<T> (like say via IList<T>) then the property is detected. But if the property is actually declared as IEnumerable<T> then it is passed over.

   I changed the line that declared ienumerableOfT from:

               let ienumerableOfT = prop.PropertyType.GetInterface ("System.Collections.Generic.IEnumerable`1")
               where ienumerableOfT != null
   

   to

               let ienumerableOfT = (prop.PropertyType.GetGenericTypeDefinition() == typeof(IEnumerable<>) ? prop.PropertyType : null)
                                   ?? prop.PropertyType.GetInterface("System.Collections.Generic.IEnumerable`1") 
   

   Kinda hacky, but it fixed the problem for me. Probably a better solution would be to recurse through the type and all inherited types till an IEnumerable<T> is found.

   The UniversalStaticDriver class does not detect the properties of the customType parameter that are directly of type IEnumerable<T>. If the customType inherits IEnumerable<T> (like say via IList<T>) then the property is detected. But if the property is actually declared as IEnumerable<T> then it is passed over.

   I changed the line that declared ienumerableOfT from:

               let ienumerableOfT = prop.PropertyType.GetInterface ("System.Collections.Generic.IEnumerable`1")
               where ienumerableOfT != null
   

   to

               let ienumerableOfT = (prop.PropertyType.GetGenericTypeDefinition() == typeof(IEnumerable<>) ? prop.PropertyType : null)
                                   ?? prop.PropertyType.GetInterface("System.Collections.Generic.IEnumerable`1") 
   

   Kinda hacky, but it fixed the problem for me. Probably a better solution would be to recurse through the type and all inherited types… more

   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…)
   1 comment  ·  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. line numbers when editing Stored Proc (beta 4.37.11 has it for queries)

   Line numbers are present in a beta release , but only for new Query windows and not when viewing/editing Stored Procs in a DB.

   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  ·  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. connect color of editor with current database

   If i work o X DB i have lightred, but i i work on Y DB i work on limegreen editor

   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

10. Update Microsoft.WindowsAzure.* assembly references to latest versions

    Obviously, features new to 1.7 (and later) will not be available as LinqPad seems to reference the 1.1 version. Also, I've been having this issue:

    Assembly 'MyAssembly, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null' uses 'Microsoft.WindowsAzure.StorageClient, Version=1.7.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' which has a higher version than referenced assembly 'Microsoft.WindowsAzure.StorageClient, Version=1.1.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'

    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

11. When copying for Markdown/Stack Overflow, find a way to add in using-directives and references

    The menu item for "Copy for Markdown/Stack Overflow" ends up copying code that in most cases won't compile without manual intervention by the person who grabs it off of Stack Overflow.

    Specifically, these two things is on the query options tab, and has to be manually added for the query code to compile and execute:

    • References
    • Using directives

    It would be nice if those two things could be copied alongside the query code, for instance as specially crafted comments at the top, that would be recognized by LINQPad upon pasting back into it, and moved to the appropriate places.

    ie.

    // reference: <RuntimeDirectory>System.Runtime.Numerics

    using System.Runtime.Numerics;

    The menu item for "Copy for Markdown/Stack Overflow" ends up copying code that in most cases won't compile without manual intervention by the person who grabs it off of Stack Overflow.

    Specifically, these two things is on the query options tab, and has to be manually added for the query code to compile and execute:

    • References
    • Using directives

    It would be nice if those two things could be copied alongside the query code, for instance as specially crafted comments at the top, that would be recognized by LINQPad upon pasting back into it, and moved to the appropriate places.

    ie.

    … more

    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

12. Always include codes outside of Main() into the selection in Program mode

    When the code fragment is selected and then F5 is pressed, LINQPad runs only selected code. I think this feature is nice.
    When I choose "C# Program" mode, of course I write some utility codes outside the Main() method.
    However, when I select the fragment of code in the Main() and press F5, the build fails, since the definitions outside the Main() wasn't included as "compile target codes".

    I think that the codes outside Main() method (in C# / VB Program mode) should be always included in compile targets to enable user-defined classes and methods,
    even if the code fragment is selected in the editor.

    When the code fragment is selected and then F5 is pressed, LINQPad runs only selected code. I think this feature is nice.
    When I choose "C# Program" mode, of course I write some utility codes outside the Main() method.
    However, when I select the fragment of code in the Main() and press F5, the build fails, since the definitions outside the Main() wasn't included as "compile target codes".

    I think that the codes outside Main() method (in C# / VB Program mode) should be always included in compile targets to enable user-defined classes and methods,
    even if the code fragment… more

    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…)
    1 comment  ·  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. Maintain a list of most recently used assemblies

    There are a few assemblies I often use in LinqPad queries, that are not in the GAC or on Nuget. Every time, I have to browse to their location to find them (e.g. Windows.winmd to use WinRT APIs). It would be nice if there was a "recently used" list in the "Additional references" tab

    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

14. LINQPad, handy scretch pad.... Why not share?

    I keep coming back to LINQPad to write few lines, execute ...verify, then go back to implement the small bit I just wrote and I am sure everyone does that and some would save those random scratch for later use or reference. So I wonder, why not a code snippet share feature directly from LINQPad? It would increase awareness and allow us share or persist some of the quick code written every now and then.

    Cheers.
    Biniam

    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…)
    1 comment  ·  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. Re-enable VS debugging for the beta

    The debugger in LINQPad 4.5 is awesome, but not as good as Visual Studio's. Before the beta, I was using Debugger.Launch/Break to debug in VS. Now, those launch LINQPad's debugger. Unless and until the debugger is as good as VS's, I would like some kind of button or something (as long as it's faster than using the preferences) to use an external debugger.

    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…)
    2 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

16. Support TIMESTAMP WITH TIME ZONE columns in Oracle

    Linqpad doesn't work very well if the underlying columns in an Oracle database contain TIMESTAMP WITH TIME ZONE columns.

    These appear in the datacontext as DateTime (losing the offset information), however queries using equality checks against them can fail due to the way the underlying IQDriver handles (or otherwise) the conversion back to datetime offset within Oracle.

    It's a bit of a pain, but one of the simple approaches is to ensure the generated SQL wraps those columns in either sysextractutc(theColumn) or 'theColumn AT TIME ZONE xxxx' to ensure they are compared with the DateTime parameter that is bound to the query.

    Obviously the better solution would be to implement them 'properly' (map to / from DateTimeOffset), but that might be more complicated

    Linqpad doesn't work very well if the underlying columns in an Oracle database contain TIMESTAMP WITH TIME ZONE columns.

    These appear in the datacontext as DateTime (losing the offset information), however queries using equality checks against them can fail due to the way the underlying IQDriver handles (or otherwise) the conversion back to datetime offset within Oracle.

    It's a bit of a pain, but one of the simple approaches is to ensure the generated SQL wraps those columns in either sysextractutc(theColumn) or 'theColumn AT TIME ZONE xxxx' to ensure they are compared with the DateTime parameter that is… more

    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…)
    1 comment  ·  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. Allow per-folder "linqpad.extensions" file

    I would like to be able to create a "My Extensions"-like file per folder so that I can create contexts or extension code that are shared by all of the queries in that folder.

    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…)
    1 comment  ·  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. Option to skip generating SQL etc. when running long running queries?

    I'm guessing this would increase speed a lot?

    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

19. samples
    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…)
    2 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. Better experience for __SOURCE_DIRECTORY__ in F#

    The FSharp compiler macro 'SOURCE_DIRECTORY' doesn't seem to behave as expected in linqpad - specifically it points to a linqpad temporary execution directory, and not where the .linq file itself resides.

    This makes it problematic to use F# type providers within linqpad. Referring to data files relative to the script is pretty common, but the path supplied to a type provider has to be a compile-time literal - ie Util.CurrentQueryPath can't be used. Absolute paths obviously break across machines.

    Not sure if a fix even is possible (I can't see anywhere on the F# compiler where you can control this behavior) but thought I'd better note it for posterity.

    The FSharp compiler macro 'SOURCE_DIRECTORY' doesn't seem to behave as expected in linqpad - specifically it points to a linqpad temporary execution directory, and not where the .linq file itself resides.

    This makes it problematic to use F# type providers within linqpad. Referring to data files relative to the script is pretty common, but the path supplied to a type provider has to be a compile-time literal - ie Util.CurrentQueryPath can't be used. Absolute paths obviously break across machines.

    Not sure if a fix even is possible (I can't see anywhere on the F# compiler where you can… more

    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