Back in August 2024, Microsoft donated (or offloaded if you wish) the Mono project to the Wine team, and now the first post-move release is out under the new name Framework Mono.
From the release announcement: "This is the first release of Framework Mono from its new home at Winehq. It includes work from the past 5 years that was never included in a stable release because no stable branch had been created in that time. Highlights are native support for ARM64 on macOS and many improvements to windows forms for X11."
What's new:
- Native support for macOS on ARM. Cis-compilation on ARM macOS is now assumed to be compiling for macOS, not cross-compiling for iOS.
- System.Windows.Forms:
- Fixed various resource leaks on X11.
- Redesigned Clipboard and Drag And Drop implementation on X11.
- Stability improvements on X11.
- Improved support for generated COM interfaces.
- Fixed some common cases where processes would hang on exit.
- Added Georgian translation.
- Many warning fixes. The Linux amd64 build no longer warns when compiling the C portion of the codebase, and this is enforced for new changes via CI.
- Many bug fixes.
For people confused on all the naming, this was also explained as there's multiple projects that use the name Mono
- Framework Mono is the project previously hosted at https://github.com/mono/mono, which was then simply called Mono. I have made this change to distinguish it from "monovm" and "Wine Mono", which are different projects. Framework Mono is a cross-platform runtime compatible with .NET Framework.
- "monovm" is a separate fork of the Mono runtime that's part of modern .NET and can be used instead of CoreCLR.
- "Wine Mono" is a downstream distribution based on Framework Mono that is used in Wine to replace .NET Framework.
And to clear up .NET:
- .NET Framework is a proprietary Windows component that supports cross-platform executable code using an object-oriented model.
- .NET Core was an open-source project supporting many of the same languages and APIs as .NET Framework but mostly incompatible with it. .NET Core was renamed to ".NET" when version 5 was released. I call it "modern .NET" to distinguish it from .NET Framework.
Read more about their goals and plans in the release announcement.
Some you may have missed, popular articles from the last month:
You can also find comments for this article on social media: Mastodon
All posts need to follow our rules. For users logged in: please hit the Report Flag icon on any post that breaks the rules or contains illegal / harmful content. Guest readers can email us for any issues.
I got dizzy reading about all the name changes.
3 Likes, Who?
It's MS, so a name change should be expected around every 3 months or so. IAM is Purview, Azure Security Centre is Defender for Cloud Apps (not to be confused with Defender for Cloud, because who could possibly get that mixed up...), Yammer is Viva Engage, Privacy is Priva, Data Service is Dataverse (barf), ATP is Defender for O365, Flow is Automate, AzureAD is Entra... the list is endless.
Genuinely endless. In another 3 months, we'll have another 15 product name changes to remember. Or ignore. People at my work still use the old names for an insane number of their products. It's just easier, since they'll change again over time.
Genuinely endless. In another 3 months, we'll have another 15 product name changes to remember. Or ignore. People at my work still use the old names for an insane number of their products. It's just easier, since they'll change again over time.
0 Likes
See more from me