Microsoft Makes Visual Studio 2022 and .NET 6 Generally Available (zdnet.com)
36
On November 8, Microsoft made generally available to users worldwide its latest versions of Visual Studio and .NET. Users can download Visual Studio 2022 and .NET 6 starting today. From a report: Visual Studio 2022 is the first release of a 64-bit version of Visual Studio. By making Visual Studio 64-bit, officials said that they expect the release to better use all system resources, especially when working with more complex solutions over longer periods. According to Microsoft, during early VS 2022 testing, customers were able to run the VS IDE for days, even with solutions containing 700 or more projects.
Visual Studio 2022 also includes a number of edits and debug improvements. It also provides Hot Reload, which allows developers to edit their source code while their apps are running in Visual Studio 2022 and from the .NET CLI. , It also has Live Preview capabilities and cross-platform testing on Linux, among other new and improved features. Visual Studio 2022 is available for immediate download. The release notes for Visual Studio 2022 v.17 are here.
Visual Studio 2022 also includes a number of edits and debug improvements. It also provides Hot Reload, which allows developers to edit their source code while their apps are running in Visual Studio 2022 and from the .NET CLI. , It also has Live Preview capabilities and cross-platform testing on Linux, among other new and improved features. Visual Studio 2022 is available for immediate download. The release notes for Visual Studio 2022 v.17 are here.
Re: (Score:3, Funny)
Would you settle for "hot mess"?
Re: (Score:3)
How does "Hot Reload" differ from "Edit & Continue" that we've had for a long time? "Edit & Continue" has been one of my favorite parts of doing C++ dev.
Re: (Score:2)
Re: (Score:2)
Re: (Score:2)
Re: (Score:2)
Does Edit & Continue work yet with 64-bit C/C++ apps? That functionality was still broken when I last worked on a 64-bit C/C++ app (VS 2017 or 2019, I think?), which drove all of us to continue targeting 32-bit for local development despite our users transitioning to 64-bit years prior, but maybe they added 64-bit E&C support in VS 2019 or VS 2022?
Re: (Score:3)
Re: (Score:2)
I've been using it in both 64 and 32 bit projects. It feels like I get errors that the edits couldn't be applied more often when in 64 bit projects, but I haven't looked into why.
Re:I wish we had hot reload in C/C++ (Score:4, Interesting)
It can be done, with difficulty. UnrealEngine does it. Handmade Hero showed how to do it in the early episodes. The basic premise is that you put most of your application logic into a shared lib with a thin executable wrapping it. When you want to hot reload, you compile a new shared lib, serialize all the application state, unload the previous shared lib, reload the new shared lib, and deserialize all the application state. It's far from trivial and requires a lot of support, but it's doable.
It works particularly well for games since game state is often fairly well-defined and can be serialized/deserialized more easily, and in games you're much more likely to be working in the part of the gameplay code that's hot-loadable, vs. say the core engine code that managed the hot loading. But again, the engine needs a lot of infrastructure to do all that.
Use more resources (Score:2)
use all system resources
Sounds about right. Going from 32 to 64 bits just about doubles the memory resource usage.
Re: (Score:1)
Microsoft can do better than that, try 10 times the memory usage!
Re: (Score:3)
try 10 times the memory usage!
But he already said that it doubles the usage...?
Re: (Score:2)
Meanwhile, in Mac land... (Score:2)
Visual Studio 2022 is the first release of a 64-bit version of Visual Studio.
I think they may mean fully 64-bit? The app itself has been 64-bit for the last few years (at least on Mac), but a lot of the libraries on which it depends have been notoriously difficult to bring to 64-bit.
Even so, this is a bit silly. So far as I can tell, Apple hasn't sold a Mac with a 32-bit processor since 2007, stopped accepting new 32-bit apps in the Mac App Store in January 2018, stopped accepting 32-bit updates to existing apps in June 2018, and outright dropped support for 32-bit apps with the rel
Re: (Score:3)
Apple has a much bigger tendency to just tell everyone to drop all the old tech and upgrade, or else. Happened with transition from PowerPC to Intel, X86 to X86-64, Objective C to Swift, and probably not long before they ditch intel/x86-64 support and make everyone jump on the M1/ARM train.
Re: (Score:2)
Re: (Score:2)
None of them. I don't think CastrTroy was implying that what Apple is doing is bad, or that what Microsoft is doing is bad. I read the post more as an explanation for why one company moves gradually and the other moves in leaps.
Re: (Score:2)
Yeah, exactly this. Neither approach is a bad idea, but they are just different approaches.
I don't see why anybody is surprised that Microsoft took so long to make a fully 64 bit visual studio release. I don't know why anybody would be surprised that Apple was switching processor architectures again.
Swift wasn't like that at all... (Score:1)
Apple has a much bigger tendency to just tell everyone to drop all the old tech and upgrade, or else. Happened with transition ...Objective C to Swift
ObjC to Swift wasn't like that at all.
They said "here's Swift, we are moving to it and you can, but do so at your own pace".
And they have over the years proceeded to upgrade ObjC with new features as well, so they are not at all pushing that you must move to Swift "or else".
They are making clear that Swift is the future but they have been pretty laid back abo
Re: Meanwhile, in Mac land... (Score:1)
Visual Studio isnâ(TM)t available on the Mac. Thereâ(TM)s some other sub-standard crap with the same name. Itâ(TM)s called brand abuse.
Re: (Score:2)
Re: (Score:2)
The problem was the immense number of plugins that were 32-bit only which forced VS to stay 32-bit.
I believe these days ti's a lot less - those 32-bit plugins will probably be tied to older versions of visual studio.
Re: (Score:2)
Also, note that Visual Studio for Mac is actually a separate product, in the sense that it started out as a rebranding of Xamarin Studio
Ah, fair enough. I've forgotten my history in such short a time.
Re: (Score:1)
Even so, this is a bit silly. So far as I can tell, Apple hasn't sold a Mac with a 32-bit processor since 2007, stopped accepting new 32-bit apps in the Mac App Store in January 2018, stopped accepting 32-bit updates to existing apps in June 2018, and outright dropped support for 32-bit apps with the release of macOS Catalina (10.14) back in October 2019.
The Microsoft code from 20 years ago that is still around can be very, very ugly. Enough that no one can work with it, and Microsoft has discontinued products entirely as a result.
That is, no one wants to work on it, and the people with the skills to actually do so, have other options.
Re: (Score:2)
On Windows the devenv.exe IDE is 32-bit (until now). It can of course compile both 32-bit and 64-bit executables.
login (Score:1, Troll)
Re: (Score:1)
At least it used to have Brief emulation so you could edit in style, but I don't think it has that now. Sadface.
Re: (Score:2)
You seem to have forgotten the dark days of the ALL CAPS menus.
Re: (Score:2)
That and at some point unity debugging broke. VS is crap these days.
It's not VS that's crap, it's Unity. Unity started migrating from the Mono compiler to IL2CPP about 5 years ago. Initially there was no support for debugging IL2CPP builds - that only came about a year or two ago. The IL2CPP debugging support ranges from "slightly useful" to "crashes constantly" depending on the platform you're targeting.
Some awesome tech in this release (Score:1)