|
Some of our devs are using 2022 now and they don't see any major issues. I think we will moving to it here soon.
for what it is worth, Microsoft is still fixing bugs with VS 2019. The VS IDE versions are never "really" ready for prime time.
|
|
|
|
|
Slacker007 wrote: Microsoft is still fixing bugs with VS 2019. The VS IDE versions are never "really" ready for prime time.
Very true!
|
|
|
|
|
VS 2017 seems to finally be stable.
|
|
|
|
|
...only because MS Devs are not really messing with it anymore.
|
|
|
|
|
We have been using it since the production release without any issues. You may have more issues moving to the new .net version than with VS itself. We are staying on .Net 4.8 with VS2022 for our desktop app, but we moved to .NET 6 for the Blazor app. No issues for us in either case.
|
|
|
|
|
GadgetNC wrote: We are staying on .Net 4.8 with VS2022 for our desktop app
The old applications are mostly desktop -- written in every version of .Net possible.
On the plus side, there is currently no listed end-date for .NET Framework 4.6.2, 4.7.x or 4.8. Current projects are all on 4.8, and I suspect all our older desktop applications will remain on 4.8 until they are rewritten, or until the end of time, whichever comes first (although "end of time" is more likely).
I assume others are facing the problem I am. How are you handling it?
|
|
|
|
|
I recently moved from VS2019 to VS2022 without any glitch.
Only one (very small) annoyance: if you keep both VS2019 and VS2022 installed, the solution file (.sln) is not automatically saved as a VS2022 solution and keeps opening in VS2019. You have to manually save it (Ctrl+S) to make it upgrade. Really small stuff.
Mircea
|
|
|
|
|
Right-click ⇒ Open With
Change the default from "Visual Studio Version Selector" to "Visual Studio 2022".
Tick the "Always open with this application" box.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
I know, but I still have a few solutions that are VS2019 and I'd like each one to open with the proper IDE. The thing with Ctrl+S worked fine.
Mircea
|
|
|
|
|
Visual Studio has been out since 1997. C# did not appear in it until 2003 2002.
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
modified 11-Feb-22 16:04pm.
|
|
|
|
|
Rick York wrote: C# did not appear in it until 2003.
Technically, C# appeared in 1988, although that version was never released: 
My History of Visual Studio (Part 1) | Microsoft Docs[^]
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
It was designed in 2000 and first released in 2003 : C Sharp (programming language) - Wikipedia[^]
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
|
|
|
|
|
So where am I? Ah yes, 1988. The project I’d been hired to work on was cancelled after a few months (I expect I’m in good company on that score), that project by the way was a cute variant on the C language designed for incremental compilation – it was called, cough, C#. Strangely, through the lens of 2009, it looks remarkably like what you would get if you tried to make C.Net.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
 That was an excellent read!  Thank You!
(kept me from actually working for > 15 minutes at least!)
"Go forth into the source" - Neal Morse
"Hope is contagious"
|
|
|
|
|
Rick York wrote: C# did not appear in it until 2003.
My archives folder shows
VS6
VS97
VS2002 (.NET 1.0)
VS2003 (.NET 1.1)
VS2005 (.NET 2.0)
.
.
.
When mounting the ISO for VS 2002, I can see most of files have a timestamp of January 2002. This is where .NET was introduced. C# was very much part of it.
|
|
|
|
|
Yes, 2002 is the correct year. I had all of those versions of VS except for 2002. I never used that one. I remember joining the MSDN and getting NT when it was in beta and installing VS97 on it. The next several years were very enjoyable.
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
|
|
|
|
|
 VS 2022 (page does not exist)
:squishing noise:
|
|
|
|
|
We migrated to it a week after release (always wait for at least the X.0.1 release!).
We've not had any issues at all with it - it's been remarkably smooth. It'll take up more memory because they (finally) converted it to 64 bit, but there's a number of gains that were realized because of that conversion.
We have a variety of applications as well, and solutions with over a hundred projects of varying types, though we've done pretty good at getting everything to be "standardized" on targeting either .Net 4.8 or .Net 6 (we did quick upgrades after release for all our .Net core based applications).
I personally like it quite a bit. They cleaned up the dark mode as well so there's no longer random bright glaring controls or panels running around.
|
|
|
|
|
VS2022 have more problems with TFS and SCE then before, and of course older problems are not solved.
I have problems building and COM registering dlls. Using VS2019 for that.
I have problems with nesting files in Solution Explorer, it was solved in VS2019, and got broken in VS2022.
Got some problems with ATL C++ project but that was fixed in an update.
As you can see I'm not happy.
Still, my org is trying to move some services to .NET 6 witch is not possible in VS2019.
|
|
|
|
|
Thanks for the feedback. In general it appears VS 2022 is fine, but from your feedback and others I've followed, there are a lot of irritating details.
Everything I'm working on is either in framework 4.8 or being migrated to 4.8, so I'm not seeing a pressing need to upgrade to 2022.
I am going to recommend to management that we look at .NET 6 for all future projects.
|
|
|
|
|
David Fenn - The Grey Crow[^]
Bit late today, but better late than never! 
Last week, I played Death's Door, one of the best indie games of 2021.
Very cool game with a pretty unique vibe and a cool soundtrack.
Basically, crows are reapers that go and collect souls of those whose time has come and you're playing as one such crow.
Of course all is not as it seems and so your adventure begins.
At one point, you fight a grey crow, and this song is the soundtrack to that fight.
The beautiful piano music is a bit of a contrast with the intensity of the fight.
Great visuals too, a completely white background with two black crows, black chains and your weapon, which is brightly colored.
Probably the most aesthetically pleasing boss fights I've ever seen and SOTW
|
|
|
|
|
Nice. the full album track has many nice songs too.
|
|
|
|
|
Yes it does!
I had a hard time picking a song (Main Theme, Ceramic Manor and Avarice are great too, for example), but I really loved the Grey Crow boss fight so I went for that one.
|
|
|
|
|
I like it
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
