Do you like VS 2022 17.2?
-
You may... I hate it and hate MS... :mad:
“Real stupidity beats artificial intelligence every time.” ― Terry Pratchett, Hogfather
-
I like you can finally navigate enumerable efficiently in the debugger. Can't say I have really looked for any other changes. The install was... a challenge with timeouts and whatnot, but that seems to have been resolved.
Do you use Git? :mad:
“Real stupidity beats artificial intelligence every time.” ― Terry Pratchett, Hogfather
-
You may... I hate it and hate MS... :mad:
“Real stupidity beats artificial intelligence every time.” ― Terry Pratchett, Hogfather
Too early to tell, only installed it a few days ago, did try a simple .NET 6 Winforms project but got into trouble when I wanted to turn off "Implicit Usings", clearly they did not anticipate someone doing that :-\ [edit] Oh, and forget trying to trim a Winforms application to reduce the exe size, that was possible in .NET 5 but not in .NET 6. So my empty Winforms app is about 160 MB :sigh:
-
You may... I hate it and hate MS... :mad:
“Real stupidity beats artificial intelligence every time.” ― Terry Pratchett, Hogfather
c++ ... new errors and warnings in the code. nothing deal breaking.
CI/CD = Continuous Impediment/Continuous Despair
-
Do you use Git? :mad:
“Real stupidity beats artificial intelligence every time.” ― Terry Pratchett, Hogfather
Yes. Do simple commit, push, pull and merge from VS, Git Extension for anything more advanced. I guess VS will eventually get to the point where i do not need a separate git ui client, but not really paying attention to it. But i have been troubleshooting since 17.2 was released, so i guess they could have messed up even pull/push without me noticing yet.
-
You may... I hate it and hate MS... :mad:
“Real stupidity beats artificial intelligence every time.” ― Terry Pratchett, Hogfather
Not sure yet..... Am working in C# desktop apps. I'm never really sure if clicking the "save all" icon actually does. Older versions like VS2019 brought up a form allowing the selection of one of multiple solutions. VS2022 only shows the most recent. AFAIK.
ed
-
You may... I hate it and hate MS... :mad:
“Real stupidity beats artificial intelligence every time.” ― Terry Pratchett, Hogfather
-
Try to switch branch while you have an uncommitted change in any file... Visual Studio Feedback[^]
“Real stupidity beats artificial intelligence every time.” ― Terry Pratchett, Hogfather
"It never ceases to amaze me that a spacecraft launched in 1977 can be fixed remotely from Earth." ― Brian Cox
-
Too early to tell, only installed it a few days ago, did try a simple .NET 6 Winforms project but got into trouble when I wanted to turn off "Implicit Usings", clearly they did not anticipate someone doing that :-\ [edit] Oh, and forget trying to trim a Winforms application to reduce the exe size, that was possible in .NET 5 but not in .NET 6. So my empty Winforms app is about 160 MB :sigh:
I love how VB has implicit usings for 20 years already :laugh: Well, it's not called as such, but it's the same.
Best, Sander Azure DevOps Succinctly (free eBook) Azure Serverless Succinctly (free eBook) Migrating Apps to the Cloud with Azure arrgh.js - Bringing LINQ to JavaScript
-
Try to switch branch while you have an uncommitted change in any file... Visual Studio Feedback[^]
“Real stupidity beats artificial intelligence every time.” ― Terry Pratchett, Hogfather
-
Try to switch branch while you have an uncommitted change in any file... Visual Studio Feedback[^]
“Real stupidity beats artificial intelligence every time.” ― Terry Pratchett, Hogfather
Define the "nothing" that the previous version would do in this case? Checking out a different branch will replace all controlled files with those from the other branch. If you have uncommitted changes which you don't want to apply to the new branch, it can either throw those changes away ("discard changes" in this new dialog), or it can store them somewhere for you to reapply later ("stash changes"). I don't think I've ever tried this, so I have no idea which of those options was chosen by default in previous version of Visual Studio.
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
-
You may... I hate it and hate MS... :mad:
“Real stupidity beats artificial intelligence every time.” ― Terry Pratchett, Hogfather
Currently on 17.1.6. I migrated from VS2017 several months ago and definitely prefer VS2022. I use GitHub, recently converted to CMake, and am working on targeting for Linux. Support for all of these things has improved considerably. Ninja compiles (C++) are ridiculously fast (~800 files in about a minute). Recently I discovered the "View" capability when looking at strings in the debugger. How long has that been around?! Probably for a decade, and I never noticed! But what a godsend when debugging the source code for template instantiations that my "compiler" (static analysis tool) has to generate. Some of the things that I don't like about VS2022 compared to VS2017: - The indent/outdent buttons for code blocks were removed. There's a way to put them back, but it's too annoying. - When I type
#include "Header.h", I always have to retype the second". Huh? - If a function defined in a header is trivial, I put the{...}on the same line, but VS inserts endlines that I have to remove. - I can't figure out how to get CMake/Ninja to do x86 compiles, so they still happen the old, slow way. - To edit an .md file in VS, you must wait until Intellisense is done, which it hardly ever is. And an .md file is none of its business! - Windows no longer allowsSIGTERMandstd::terminateto be caught in a release build. - There are probably other things, so I'll try to edit them into this post as I'm reminded of them. Someone might know how to overcome them.Robust Services Core | Software Techniques for Lemmings | Articles
The fox knows many things, but the hedgehog knows one big thing. -
Define the "nothing" that the previous version would do in this case? Checking out a different branch will replace all controlled files with those from the other branch. If you have uncommitted changes which you don't want to apply to the new branch, it can either throw those changes away ("discard changes" in this new dialog), or it can store them somewhere for you to reapply later ("stash changes"). I don't think I've ever tried this, so I have no idea which of those options was chosen by default in previous version of Visual Studio.
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
Not exactly - working with git (without the VS wrap), while creating a new branch (on the local) and than switch to it, the uncommitted changes will stay uncommitted... The new branch is an exact copy of it's parent, which includes the uncommitted change - and that's what I call 'nothing'... While I can see that some can benefit from the check VS now runs, the fact that I can't turn the popup off is annoying... Plus, take in account that the check VS does is far from being complete, the current (base) branch in my case is write protected so committing to it is futile... Also the newly created branch is local so no danger of whatsoever to ruin something...
“Real stupidity beats artificial intelligence every time.” ― Terry Pratchett, Hogfather
-
Try to switch branch while you have an uncommitted change in any file... Visual Studio Feedback[^]
“Real stupidity beats artificial intelligence every time.” ― Terry Pratchett, Hogfather
-
It does the same with VS2017.
- I would love to change the world, but they won’t give me the source code.
Not for me! It is the very first time I saw it...
“Real stupidity beats artificial intelligence every time.” ― Terry Pratchett, Hogfather
-
You may... I hate it and hate MS... :mad:
“Real stupidity beats artificial intelligence every time.” ― Terry Pratchett, Hogfather
I'm on 17.0.2 - never bothered with the incremental updates since initial install. Other than file level history/blame, I don't use the built in GIT features in VS, so your issue would have no impact on me. Not being able to set a default and only pop that when it won't work does suck though. X| Have an upvote on your issue on the MS side though.:thumbsup:
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, weighing all things in the balance of reason? Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful? --Zachris Topelius
-
You may... I hate it and hate MS... :mad:
“Real stupidity beats artificial intelligence every time.” ― Terry Pratchett, Hogfather
I use VS mostly for C++ code, and the compiler seems to work just as well as the compiler in VS 2019, i.e. I haven't discovered any new bugs. I haven't tried the new C++20 features yet. I also haven't spotted any new bugs in the IDE. I haven't tried your particular 'git' scenario, so I can't comment.
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows. -- 6079 Smith W.
-
Not exactly - working with git (without the VS wrap), while creating a new branch (on the local) and than switch to it, the uncommitted changes will stay uncommitted... The new branch is an exact copy of it's parent, which includes the uncommitted change - and that's what I call 'nothing'... While I can see that some can benefit from the check VS now runs, the fact that I can't turn the popup off is annoying... Plus, take in account that the check VS does is far from being complete, the current (base) branch in my case is write protected so committing to it is futile... Also the newly created branch is local so no danger of whatsoever to ruin something...
“Real stupidity beats artificial intelligence every time.” ― Terry Pratchett, Hogfather
So the "bring the changes to..." option from the new dialog, which appears to be selected by default? I can see how you might be slightly annoyed that you can't configure a default action and suppress the dialog. But it's hardly an "unable to use this version"-level bug. :)
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
"These people looked deep within my soul and assigned me a number based on the order in which I joined" - Homer
-
So the "bring the changes to..." option from the new dialog, which appears to be selected by default? I can see how you might be slightly annoyed that you can't configure a default action and suppress the dialog. But it's hardly an "unable to use this version"-level bug. :)
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
The first option is the default - and that what I want... And I change branches like 20 times a day (on 4-5 different projects) and it is beyond annoying... I filled the "can't use" option to try to make MS to take it more seriously... because of my past experience...
“Real stupidity beats artificial intelligence every time.” ― Terry Pratchett, Hogfather
-
Too early to tell, only installed it a few days ago, did try a simple .NET 6 Winforms project but got into trouble when I wanted to turn off "Implicit Usings", clearly they did not anticipate someone doing that :-\ [edit] Oh, and forget trying to trim a Winforms application to reduce the exe size, that was possible in .NET 5 but not in .NET 6. So my empty Winforms app is about 160 MB :sigh:
RickZeeland wrote:
So my empty Winforms app is about 160 MB
What the flaming :elephant:?
Software Zen:
delete this;
