I think this could be extended beyond an immediate window replacement. It could be defining a new category of tooling.

I've noticed a tendency to use test runners and unit test tools as exploration tools and simple automation tasks. Projects having lots of small [Explicit] tests (or just useless tests) that serve no other purpose than for debugging and understanding a piece of functionality while interacting with it.

Integrating linqpad into vs could define a category of tooling for this kind of code where benchmarking and other diagnostics tools for interactive exploration of some aspect take priority over executing and validating lots and lots of invariants.

I definitely agree this should be a feature. It's actually quite cumbersome having to leave the VS environment to go to a separate application just to quickly jot some code down to see if it might work.

Wow, almost 900 votes. Still nothing!

Is it possible to make it as Resharper plugin? As a bonus crossplatform Project Rider support.

There is already a workaround available for this, read more at Stackoverflow:
http://stackoverflow.com/a/38199055/1016343

How about to Integrate into VS Code? https://code.visualstudio.com/

Something like what Devart's LINQ Insight does?

I regard Linqpad as a VS Lite. So integrating into VS doesn't make it a scratchpad anymore. I use it to test code because it launches faster. Then I use the code in VS when I'm satisfied with it.

why not implement your 'script' as a TestMethod in a TestClass / Project.

you got executing of what you want, all benefit of VS without create a full application for a small piece of code that you want to execute?

Heh, I spend more time writing code in linqpad and then moving it to VS. I'd prefer more VS features integrated into Linqpad :)

Simply put... this would be awsome

it's not a full Visual Studio integration but more like a Bridge between the two and I think it would help a bit for debugging process.

http://visualstudiogallery.msdn.microsoft.com/8ede652c-396f-4dc9-bc4f-c88f9b8291d2

It's still under development, but it's (hopefully) quite stable. Any feedback is appreciated.

Integration into the Visual Studio IDE would make a great product, an awesome product.

You might be able to author a VS extension that creates a .linq file for the block of code that is selected in VS? You might be able to also grab the references and namespaces from the related file and add them to the .linq file as well? Then, you might be able to open your nifty new .linq file and execute it?

I was able to add LINQPad to the 'External Tools' list in VS and pass it the $(ItemPath) argument. This launches the entire file in LINQPad but isn't ideal.

Agreed, wholeheartedly; linqpad would make the perfect immediate window replacement.

LinqPad as DebuggerVisualizer tool would be very cool feature for datashaping of large datasets or collections.

Yes it would really make analyzing and debugging Linq queries much more convenient.

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 ...

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.....

To be able to place my cursor inside a linq query in VS and hit a magical set of key strokes and have my linq query transfered into LingPad would save me hours!!! Especially if all the references (dlls, etc.) from VS applied to LinqPad.

Then when my LinqPad work is done, press a key and my linq query is transfered back into VS! WOW!!!! I want this yesterday!