Given the PR called out in this issue https://github.com/dotnet/project-system/issues/223, "Initialize Interaction with Project" now shows up for the new project system if target .NET Framework in 15.8. The menu is hidden when targeting other platforms.
The project system work is done, the rest of this work is on Roslyn's side.
Note, this is basically a new version of the bug @shaggygi filed here https://github.com/dotnet/roslyn/issues/11684.
And then there is https://github.com/dotnet/roslyn/issues/19050 where @kuhlenh filed. :laughing:
Any progress on this? I just ran into it.
This a feature request in the Unknown milestone meaning that it has not been scheduled.
Got 2019 RC, and this feature did not make it :/
It is on unknown milestone so don't think it is implemented yet.
This is very helpful when I'm trying to one-off something for a quick POC. I can't wait to get it back!!!
Why is this roslyn instead of IDE?
Any update on this? This is such a useful feature!
Yet another thing that I went to use in VS that has been available for previous versions and frameworks that is now missing.
Rewriting the entirety of netfx into a wholly different framework and codebase instead of refactoring in place was a really dumb and costly decision. Add this cost to that bucket and to the customer dissatisfaction bucket.
There's lots missing from original objectives with the C# REPL. Would love to see NuGet support. I heard the plan was to take what was learned from F# Interactive and add to C# flavor at some point. Any roadmaps/discussions?
Here's hoping this gets more traction soon. C#-Interactive is awesome to quickly try things before trying it in an actual project and compile 15 times before getting it to work.
For how long coreFx and netstandard have been around, this has been long overdue.
Any update on this?
Still relevant
Without this feature, the c# repl is essentially just a toy for core developers, which is kind of a shame.
Funny I was directed here from Microsoft site to upvote and there in no voting button. +1
@dmikov on the main post, click the smiley and the thumb up/down
Come on guys, it is kind of rude to let the community hang like this.
Throw us an update!
Doesn't anybody at Microsoft actually use C# Interactive? I'm not sure how to explain two years of inaction on this other than "nah, we all use LINQPad over here".
Yeah, this is quite inexcusable. It's a no-brainer feature, but I should really call the lack of support here a bug. We're having to use Jupyter notebooks with C# interactive so that we can import nuget dependencies for the project. That's just ridiculous :)
@terrajobst @KathleenDollard @kendrahavens @cartermp @jonsequitur @LadyNaggaga
If possible, could somebody on the team provide insight on the future of C# Interactive and related tooling for Visual Studio? It just seems like there has not been any love or clear explanation on roadmap (please forgive if I've overlooked).
For example, still looking for debugging with scripting, NuGet package, and .NET Core (partly with this issue) support.
Could someone offer some time during one of the YouTube sessions to provide an update?
Any updates will be appreciated.
@tmat was the fix for this ever merged?
We have added support for running Interactive Window on .NET Core in 16.8 Preview 1, which is a prerequisite for this feature. Next step would be to wire up the command in CPS based project system integration.
We have added support for running Interactive Window on .NET Core in 16.8 Preview 1, which is a prerequisite for this feature. Next step would be to wire up the command in CPS based project system integration.
Is there any way to select the Core SDK version? Trying to use 5.0 preview/RC won't work as it uses 3.1 automatically.
Most helpful comment
Any progress on this? I just ran into it.