Never call me unfair.

A few years(!!) ago, I ranted about how you had to update the visual studio updater before you could update visual studio (which I still think is a valid rant)

Today I noticed that the visual studio installer just does this itself silently now. Therefore, I choose to apply praise to this welcome change and in the name of justice and fairness, recognize this vast improvement.

*ahem*.... GG VS2022

Ahh yes Visual Studio, gotta make sure it’s extra-private.

<updating Visual Studio 2022 in virtual environment>
VS: now done, you have to restart your computer
<restarts computer>
<starts VS2022>
VS: nice that you are using an update, we want you to log into your M$ account
VS: here is a window where you can log in
<uses window to login with email+pwd>
VS: YOUR ORGANIZATION NEEDS TO UPDATE THE BROWSER, IT'S TOO OLD!!! ARRGGGGGHHHHH
...

VS never ceases to amaze me.
What's the point of a FUCKING IDE that
suggests compilation errors with its autocomplete?

What's the fucking point!?

CommandTimeout is an int, not a TimeSpan.
I want autocomplete to HELP ME, not to waste my time with irrelevant noise based on on some AI bullshit.

I want to know who are the motherfuckers who thought this was a good idea. I fucking hate them.

Does someone know how to disable this shit? I disabled everything in Options->Intellicode, but that shit keeps popping up.

Visual Studio 2022, btw

Now I'm a bit impressed by auto complete of VS2022.

The full text in grey is auto complete proposition.

Back story :
I have a table where datetime is stored as nvarchar(max).
I'm trying to convert that shit into a proper datetime2 column
But there are dates in ISO format, there are in MM/dd/yyyy, dd/MM/yyyy and there are some with hours/minutes parts.

So i'm making a little script to clean of all that up.
Ofc, not a perfect result, like 01/02/2022 will be considered as dd/MM/yyyy (98% of values are. But still cleaner than before

There an ambiguity between VS2019 and VS2022
VS2019 simply works, and VS2022 is slow and full of bugs and MS keep telling they don't see the problem.

So I did nothing to this file, except adding one more test method and all of a sudden when code was broken elsewhere VS started to hard complain, fixed elsewhere compilation, but stuck with this

I'm doing it !

I WILL run current PROD projects in a preview 1. (Well, at least I will try).

Wish me luck !

VS2022 is an abomination......

I was forced to put the whole team on 2019 ansd remove all .net 6....

VS2022 is NOT USABLE AT ALL !

It's like vs2010 which we all skipped.

I'll wait for VS 2024 at this point...

can't work. "Changed a file" ? Oh wait i'll just recompile whole solution for 3 minmutes at EACH FUCKING FILE CHANGE.

VS2019 9Same project) : 0.2 seconds.

Recently saw that Visual Studio 2022 preview build, I guess 4 is here, so any idea if this one is more stable? Like I had the 3rd preview build and sh!t was the worst. Felt like riding a bullock cart. Even the indent guides vanished outta nowhere. So guys?