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
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.
-
You may... I hate it and hate MS... :mad:
“Real stupidity beats artificial intelligence every time.” ― Terry Pratchett, Hogfather
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 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.
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.
-
Do you use Git? :mad:
“Real stupidity beats artificial intelligence every time.” ― Terry Pratchett, Hogfather
-
Do you use Git? :mad:
“Real stupidity beats artificial intelligence every time.” ― Terry Pratchett, Hogfather
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.
-
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
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.
-
You may... I hate it and hate MS... :mad:
“Real stupidity beats artificial intelligence every time.” ― Terry Pratchett, Hogfather
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
-
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
-
You may... I hate it and hate MS... :mad:
“Real stupidity beats artificial intelligence every time.” ― Terry Pratchett, Hogfather
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
-
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 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.
-
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
