|
dan!sh wrote: Latest VS would give you the clap for you when you do this
FTFY
Software Zen: delete this;
|
|
|
|
|
My most common typing error involves NOW/NOT.
i.e.: "I will now initiate the re-installation."
|
|
|
|
|
That's the typo managers would love - "I would now do what you said."
"It is easy to decipher extraterrestrial signals after deciphering Javascript and VB6 themselves.", ISanti[ ^]
|
|
|
|
|
You may... I hate it and hate MS... 
“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?
“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.
|
|
|
|
|
Not using but I'm assuming the 2 main announces still not changed, but I'm not aware of anything big change in 17.2 that not been in since 17.0
Basic Check changes, stage, commit, merge, conflict fixing all works, unless you the smart alic coworker that shoves in squish and other headach commits.
Method intelisense of when last edit and who. Blame. All functions in editor without having to load another tool.
2 issues:
1. switching branches in the git manage throws another tab. Wtf why cant you stay on the manage tab.
2. why the view single commit history have the changes files list fixed into the side by side view. The old git had all simple in the git changes menu which was a better navigation for me at least.
|
|
|
|
|
We are still on 2019 and waiting for the dust to settle on some critical project releases before we look at 2022.
We use Git with DevOps through VS. What have they done to it?
If you think 'goto' is evil, try writing an Assembly program without JMP.
|
|
|
|
|
Of course, I use Git. But I recently had to restore my workstation from a backup after replacing the hard drive, and Git somehow lost my Git files, even though they were still there. So, while I saw some magic commands some suggested, I didn't trust or understand them, so I just wiped my applications one at a time, and re-cloned them from DevOps.
|
|
|
|
|
I honestly think they are trying to make it better with every release.
But, it seems they changed the directory name for C# user-defined project/item templates from 'Visual C#' to just 'C#'. I spent about 30 minutes trying to figure out why my item templates disappeared. I didn't see that talked about anywhere.
|
|
|
|
|
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 
modified 12-May-22 9:28am.
|
|
|
|
|
I love how VB has implicit usings for 20 years already 
Well, it's not called as such, but it's the same.
|
|
|
|
|
|
RickZeeland wrote: So my empty Winforms app is about 160 MB
What the flaming ![Elephant | [mastadon]](https://codeproject.global.ssl.fastly.net/script/Forums/Images/elephant.gif) ?
Software Zen: delete this;
|
|
|
|
|
|
I thought I would like the implicit/global using stuff. I do not like it so much.
Ctrl-r-g had become a matter of habit. I'm not sure what I've really gained. Less scrolling to get to "meat"? For the seasoned, it isn't horrible.
For the new, it might be better/easier. So many examples out there are going to have things "the old way" though.
It's also a bit jarring to have an args on a console app with implicit Main()...
Who wouldn't be right to go, "args? What args? There are no args here? Is args a special keyword?"
Similarly with namespaces. I'm not so sure I'm as big a fan of tucking these things away as I first thought I might be when only reading about them instead of actually seeing them in practice.
|
|
|
|
|
c++ ... new errors and warnings in the code.
nothing deal breaking.
CI/CD = Continuous Impediment/Continuous Despair
|
|
|
|
|
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
|
|
|
|
|
Yes, so far it's working well.
Any reason you don't?
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
