Skip to content
← LINQPad Feature Suggestions

I suggest you ...

LINQPad Feature Suggestions

Categories

(thinking…)

Use LinqPad as Immediate or Watch window (Debug) in VS

I want to be able to debug using Linq and lambda expressions. I`m missing this very much in VS

21 votes
Vote

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
You have left! (?) (thinking…)
Iurii shared this idea  ·   ·  Report…  ·  Admin →
How important is this to you?

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • mike commented  ·   ·  Report

    I came here to suggest this. It would be fantastic to have a VS plugin that can launch Linqpad and pass it the VS debugging session. Then, when you are trying to figure out what the problem is, Linqpad can be used to interrogate the session.

    In my mind this would be so useful it would be worth buying it just for that.

  • Anonymous commented  ·   ·  Report

    This is a big reason to use LinqPad in itself. It's the only missing piece. Otherwise, you must put .Dump() on every property or .Select(p => p.someproperty).Dump(). It's pretty tedious. I've been using LinqPad with the Open XML SDK. It shows no values, just that objects are present.