9 ms·
Honestly surprised that Microsoft have not bought this up and integrated it into Visual Studio. LINQPad is gold.
by CodeCompost 2y ago
Honestly surprised that Microsoft have not bought this up and integrated it into Visual Studio. LINQPad is gold.
- atlantic 2y agoThere is already a C# REPL built into Visual Studio, called C# Interactive. It takes a bit of getting used to, but it's not bad at all.
- deleted 2y ago[deleted]
- recursive 2y agoNot even in the same zip code.
- mattmanser 2y agoEchoing the other comment, personally I find the C# interactive really frustrating to use. So close and yet so far. I often find it quicker/less frustrating to just fire up a new console app project. Last time I tried to use it I think it was even running an old version of .Net and you have to remember to switch the version.
- celdon25 2y agoI'd say it is pretty bad[1], but the F# REPL is decent at least. 1. https://github.com/dotnet/roslyn/issues/26934 https://github.com/dotnet/roslyn/issues/26934
- misterflibble 2y agoYes I saw the REPL in VS 2022 and Jetbrains Rider, but I still prefer having this utility at hand with a collection of scripts ready whenever I need to script up something, or experiment with a service or database, or learn something new in .NET.
- fbdab103 2y agoThat is true of so many products. Notepad++, Paint.Net, Everything search. Products which would cost Microsoft absolute peanuts to acquire. Or even just use that as a model and rip it off entirely with an in house version.
- gwervc 2y agoIt's because Microsoft isn't really serious with C#. For years it has advertised other languages (e.g. JS on WinRT) or runtime (wasm), support in VS Code is still rather interesting, UI frameworks were never made truly multiplatform and the one which supposedly is is still buggy as hell (maui). C# 12 is a pile of crap (C# 13 looks interesting tho). So in the end it's good all those tools stay independent and focused.
- oldmanhorton 2y agoI don't think it's true that C# isn't taken seriously at Microsoft - some of the frameworks on top of C# come and go, but I worked on JS on WinRT briefly and can say it was never, ever "taken seriously" in the way the core C# language and runtime is. If you want to work with azure or windows, C# will be the obvious best choice for the foreseeable future, and if you want to work with C# outside of those verticals I don't think it's a bad or dead end choice either.
- mandeepj 2y ago> It's because Microsoft isn't really serious with C# OP is speaking out of thin air. It's one of the best programming languages out there.
- devjab 2y agoBest at what exactly? I can’t think of a single thing you would pick C# for instead of Java/Go, C/C++/Rust/Zig, Python or JavaScript/Typescript. Not because C# is a bad language but because it’s not particularly good at anything. It’s a jack-of-all trades which isn’t even the best jack-of-all trades. So unless you have a lot of years put into it, either in your software stack or in your employees there is very little reason to use it in 2024. But maybe you know of reasons to use that I’m not aware of?
- rqtwteye 2y agoI am glad that they haven't. Usually only a butchered version gets integrated or it gets abandoned after a while.
- misterflibble 2y agoLINQPad is probably the most useful mini-IDE that I've ever used and I employ it every single day for .NET prototyping, scripting and experimenting. Joe Albahari's done a great thing with this utility!