15

I only created a fucking class, a FUCKING EMPTY CLASS

Cancel button does nothing, obviously.
After 30 seconds or so, everything is back to normal. This shit reminds me of the "good old days" with Eclipse.
I hated Eclipse back then, and I fucking hate VS now

Comments
  • 0
    are you using vs for Java? or C++? I anticipate Java
  • 1
    @C-sucks C#! Dotnet 5
  • 0
    @catgirldev 2019
  • 5
    Hasn't VS always been like this?
  • 0
    @tonypolik uhg working with C#, .net framework 4.8 in VS 2022...

    Everything works fine.

    Never used the core one. Is it so much different ?
  • 0
    @Grumm VS itself is the same. Dotnet 5 is a major improvement from .net framework, but it's a different topic 🙂

    This shit does not happen everytime I create a class (thank GOD). Sometimes it does, and it happens way too much for my taste
  • 0
    @tonypolik Damn microsoft. Made a windows app in 2019 using DotNet framework.

    I should port it to the new Core when I have some free time :D
  • 0
    I never get anything like that. Have you got a dodgy extension or is antivirus gobbling up your resources?
  • 0
    @TrevorTheRat i have the containers tool extension because i run docker.
    It appears randomly even when cpu is running fine. Lucky you :-)
  • 3
    How DARE you asking bs to create a class? It is right to ransom your pc. I am a loss of words for such an efferate act!

    What is next? Are you gonna ask unity to refresh a scene? Jeez!
  • 2
    @piratefox Right ! who needs classes...

    One file is enough (the one that vs already made... how nice is that)
  • 1
    @Grumm how are you going to flex the amount of lines of code in your application otherwise? Just screenshot the last line, duh!
  • 1
    @c3r38r170
    (i know this isn't an argument, it's not supposed to be, just a surprised observation)

    no, in my 10 or so years of using VS, since 2015 (or whichever it was at the start, i can't remember the numbering before 2015) up to 22, for C#, but also typescript and html, i never had basically any problems with it.

    okay, one, in 2019, where ctrl+z that removed or added a block of code occasionally triggered a 15-25 second progressbar.

    other than that, literally never had any issues with VS.
Add Comment