Install .net -> install vs code -> install C# vscode extension:
extension not working.
Great job Microsoft!
Booting back to Linux partition.

  • 7
    Definitely the fault of Windows. couldn't be a n y t h i n g else
  • 1
    There are some dotnet test frameworks which aren't entirely FOSS (though they are OS) which is why vanilla installs often don't include them and you have to explicitly install them yourself.

    And you need to define your launch.json, I guess.
  • 3
    Get visual studio community.
    Vscode is not mean for that stuff.
  • 4
    You must be a one of those mythical rock star devs.

    You gave up immediately without even trying to find out why it didn't work.

    Not gatekeeping here, but a dev should have the drive to fix and investigate things. That's the first requirement of a good dev in my opinion.
  • 2
    Yeah same. Installed linux, booted ; No gui !!! Back to windows.
  • 0
    @MrCSharp I get some of the aspects.
    More and more if the tool doesn’t do what I want it to do out of box, I don’t search for more than 5 minutes.
    Good tools should provide everything needed from scratch without any “addons” etc. “:Addons” are QoL things.
    If you need a plugin, just to write code, it’s a bad tool.
    I have example of my own. Was looking for a good Git management tool. git kraken was a nice thing on paper. Installed. Cannot delete multiple branches. Uninstalled. The ONLY thing I wanted is to delete multiple branches.
  • 2
    @NoToJavaScript You dont need a CSharp tool to write CSharp in VS Code. You do need an addon to compile and run it though, but that is a QoL thing because VS Code is marketed as an editor, not an IDE
  • 1
    @frogstair Yes I agree.
    So for a new comer to windows/c# I would recommend Visual Studio. Yes, it is not as fast, but you get everything needed (and more) out of box.
  • 1
    I mean, if you just install the dotnet ask, it'll ship with a capable msbuild configuration. So building is fairly trivial even without a plugin.
  • 1
    @NoToJavaScript This philosophy denies all tools that are primarily designed for experts' convenience and don't try to be similar to anything. Adobe CC is a nightmare to learn, not because they suck but because they are built for people who are willing to invest a lot of time in learning them.

    If you want to be an expert at something, spending hours up to months learning about the internal logic of the tools before you become as efficient as you were previously isn't a big deal, because on the long run it will pay off.

    Linux doesn't have a good GUI and fails to show one in some scenarios not because it sucks, but because it isn't focused at the gui. That doesn't mean you can't get it to have a fantastic UX tailored to your workflows, given enough time and effort.

    If you don't care about using it enough to troubleshoot the GUI, it's probably for the better because you were gonna meet much bigger obstacles way before you reached your previous, windows based level of convenience.
  • 1
    @NoToJavaScript As for the addons, that's just a term. Every GUI app is as much an addon to windows as vscode addons are, because vscode isn't meant to be used without addons. It's a framework, if you will, for code editors. It provides all the general tools and nothing specific, such that you don't have to download and run stuff you were never going to use anyway and plugin authors don't have to write their own code for buffering text or showing a GUI.
  • 0
    @Ranchu This. +1
  • 0
    @MrCSharp Fix things when they're broken, which is not the state I expect them to be in after fresh install.
Add Comment