Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API

From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Search - "vs2022"
-
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 VS20224 -
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, btw6 -
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 before1 -
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 this1 -
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.8