Settings and activity

  1. 1,212 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    22 comments  ·  LINQPad Feature Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
    Raimonds supported this idea  · 
  2. 1,090 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    21 comments  ·  LINQPad Feature Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Raimonds commented  · 

    In addition to previous:
    Of course, debug-time access to variables, properies and methods, like immediate window functionality, is a MUST thing, due to poorly immediate window functionality.
    And so on ...

    Raimonds supported this idea  · 
    An error occurred while saving the comment
    Raimonds commented  · 

    Great idea! But this can be very complicated thing. In fact, to be useful, that addin MUST get NS references from current project, as well independently parse project code, even not yet compiled, ability to access not public members would be welcome. As result we can not to always do 'copy - paste - edit - adjust - test' cycle, but, for example, simply type in LinqPAD pane something like "new SampleClass.SomeProtectedMethod(anything)"....
    In this situation you don't need more copy back corrected code fragments, they will be already edited inplace!
    REAL time-saver.
    But likely this is too nice to be truth .... :(
    However, this can be GREAT value for what i'll want to pay, much more than autocomplete in LinqPAD standalone version.....

  3. 8 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  LINQPad Feature Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
    Raimonds shared this idea  ·