|
I've mostly used SourceTree instead of VS, but that looks like a useful feature actually. It would be nice if it was more configurable, I can understand why you would get annoyed with not being able to change it.
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
Am I missing something? That is normal Git behavior. Its bash shell will give you a warning about switching branches with un-commited changes, and if you change anyway you'll permanently lose those changes unless you stash them first. Why shouldn't VS do the same (if it doesn't already)?
If you think 'goto' is evil, try writing an Assembly program without JMP.
|
|
|
|
|
We are talking of a case when creating a new branch (local) from an existing branch (local) - no way of any lost content, and Git knows it and does not disturb you... VS didn't do it either up until I updated to 17.2
“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 allows
SIGTERM and std::terminate to 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.
|
|
|
|
|
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.  Have an upvote on your issue on the MS side though.
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
|
|
|
|
|
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.
|
|
|
|
|
The problem with hate is, it's a destructive motion after all. True, there's nothing bringing people together like the hate for a common enemy but take this hate away and you're left with shambles. Like, nazis & tree huggers marching together against COVID-19 measures may be the best friends but last time we (Germany) had nazis in power, tree huggers were among the first ones to "let go".
Specifically to Visual Studio, I've seen hate so stupid, it hurts. Like that article I got in my CodeProject newsletter from a nutjob proclaiming Visual Studio is to blame why there's no decent IDEs/code editors for .NET. Like, WTF?
That said, type hints for C++ in the latest VS are amazing! I'm also a huge fan of test coverage right within the text editor, but that's not new to the latest VS.
|
|
|
|
|
Used to VS but I use it only for editing, compiling and debugging - everything else is run outside of VS.
|
|
|
|
|
Why? I like it. Compared with Xcode (which I also use, on the Mac of course) it's in a different league. MS keep breaking Edit n Continue though, which means I am back on VS 2017, pro-tem.
Paul Sanders.
Some of my best work is in the undo buffer.
|
|
|
|
|
I use vscode. It's not a real ide, I guess, but it does what I want, and that is enough for me. I'm very old school about debugging anyway, and mind my own git separately.
Maybe VS is like a fancy bread maker that I don't need because my KitchenAid, huge crockery bowl, and oven can do the job nicely.
|
|
|
|
|
I uninstalled VS 2022 because it completely messed up my VS 2019 environment. I found that I couldn't find my standard .NET Framework versions and I am using 4.6 in my current development project.
I had to uninstall every thing just to get my work back in VS 2019.
It turned out that it appears that VS 2022 changes the way the project templates are displayed making the .NET Framework templates more confusing to find.
The VS 2022 installation did this to VS 2019 as well.
Steve Naidamast
Sr. Software Engineer
Black Falcon Software, Inc.
blackfalconsoftware@outlook.com
|
|
|
|
|
I do not manage big projects like most of you.
That said I started with an Apple /// and basic OK YES time marches on and we get improvements in IDE's
But the old saying "If it ain't broke don't fix it" seems to have escaped Microsoft.
My experience with going from VB 6 to Visual Studio was a challenge because I am a novice.
But it seems every time Microsoft makes an improvement they let us be the beta test dummy.
The company IMHO has lost the trust of the user but in a way they own us as users.
New and improved is not always true when dealing with Microsoft
|
|
|
|
|
Wicked Poles - 99 of them!(8)
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Balloons 
Life should not be a journey to the grave with the intention of arriving safely in a pretty and well-preserved body, but rather to skid in broadside in a cloud of smoke, thoroughly used up, totally worn out, and loudly proclaiming “Wow! What a Ride!" - Hunter S Thompson - RIP
|
|
|
|
|
Nina would be ashamed of you!
Nope.
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
It seems CCC slowly turns into a Welsh internal affair... 
“Real stupidity beats artificial intelligence every time.”
― Terry Pratchett, Hogfather
|
|
|
|
|
Siaradwch Cymraeg os gwelwch yn dda.
|
|
|
|
|
ביום אתה מדבר עברית...
“Real stupidity beats artificial intelligence every time.”
― Terry Pratchett, Hogfather
|
|
|
|
|
Diolch
Life should not be a journey to the grave with the intention of arriving safely in a pretty and well-preserved body, but rather to skid in broadside in a cloud of smoke, thoroughly used up, totally worn out, and loudly proclaiming “Wow! What a Ride!" - Hunter S Thompson - RIP
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
