10

During 6 months I updated myself day and night on java, springboot and AWS.

I failed most of the technical interviews on my preferred stack, however I got a job, where the probable stack is C#, dotnet and Azure.

So, I have a couple of weeks of very good quality rant ahead.

I just started.

hmmm let's see, should I use Visual Studio or Visual Studio CODE. I spent the morning before understanding they were different. I could have spent the morning Studying how To Visually fuck you, lame name chooser.

Now I'm following a tutorial.
I need .NET 5.0, but guess what, I have .NET core 3.1.
But wait, fuck, .NET and .NET CORE are not the same thing! Will .net core 3.1 work for a .NET project or not?

And there goes the afternoon. Is he the same guy who choose the names?
I'll tie you with a barbed wire net and fuck you to the core, you asshole

Comments
  • 3
    holy fuck, there is also .NET fuckwork. Is this a Kamasutra of Dev or what?
  • 4
    I entered in rantoverflow mode.

    I just decided to use Visual Studio Code, and download .NET 5.0.

    And I see a nice message "this release is only compatible with Visual Studio 2019"

    WTF
  • 3
    ++ worthy content right here

    I look forward to your next angry rants
  • 3
    .NET framework was (mostly) merged into .NET core with .NET 5.0.
  • 2
    Welcome to the .NET maze
  • 2
    Yeah .net is in a chaotic state right now, as it's undergoing quite some change

    But about the compatibility thing: it shouldn't matter what visual studio version is compatible, if you use visual studio code
    The C# extension for vscode *should* just work out of the box

    Now I don't know if the place you woke at does this, but I can recommend turning on nullable reference types in the project settings. That way the compiler will give you sophisticated code analysis about possible null objects being passed around.
  • 1
    @LotsOfCaffeine @willcandy
    The VS Code extension should complain and offer a link if it misses something.
Add Comment