21–30 of 84 posts
"net5.0-windows (and later net6.0-android and net6.0-ios). These TFMs represent OS-specific flavors of .NET 5 that include net5.0 plus OS-specific functionality." Wait - net6.0- is actually net5.0?
"net5.0-windows (and later net6.0-android and net6.0-ios). These TFMs represent OS-specific flavors of .NET 5 that include net5.0 plus OS-specific functionality." Wait - net6.0- is actually net5.0?
My reading of this is that Xamarin has been dropped from .NET 5 and moved to .NET 6, and Microsoft is hoping you don't notice.
.NET Standard was confusing, and the ubiquitous TFMs in the early days were even more so. But all of those struggles where made to achieve a cross-runtime compatibility layer to make it easier to support both ecosystems. It was a Herculean effort by Microsoft, and they achieved it.
Now it's purpose has been served and as we move forward we can all just use the simple name of netX.Y, unless we're library authors that want to continue to support legacy .NET Framework as well.
Earlier articles in this ongoing series of “how to name things”: - September 2016: Introducing .NET Standard ( https://devblogs.microsoft.com/dotnet/introducing-net-standa... ) - May 2019: .NET Core is the Future of .NET ( https://devblogs.microsoft.com/dotnet/net-core-is-the-future... ) - May 2019: Introducing .NET 5 ( https://devblogs.microsoft.com/dotnet/introducing-net-5/ ) (Yes, the last two are from the same mo…
What’s so weird is that DirectX has an entirely terrestrial naming system and .NET refuses to follow its example.
"net5.0-windows (and later net6.0-android and net6.0-ios). These TFMs represent OS-specific flavors of .NET 5 that include net5.0 plus OS-specific functionality." Wait - net6.0- is actually net5.0?
This is good news for experienced .NET developers and newcomers alike. It marks the end of the journey from legacy .NET Framework to fully open source cross-platform .NET. .NET Standard was confusing, and the ubiquitous TFMs in the early days were even more so. But all of those struggles where made to achieve a cross-runtime compatibility layer to make it easier to support both ecosystems. It was a Herculean effort b…
Also, there is still very popular Unity 3D, that can target later framework, but will continue to run on the legacy one itself for a while.
This is the most schizophrenic platform I've ever worked on. I've just spent an hour trying to make something work across the five different variants and web pipelines doing things underneath. Edit: to be clear we have completely hung legacy stuff which is waiting resources (lots of $$$$ wasted) to port it to later versions of the frameworks because huge chunks of the ecosystem got abandoned by MS and the OSS develop…
I personally felt .Net standard was a great investment in making a standard platform that the community could contribute to, that would, of course, move slower than the giant monolith controlled by Microsoft... but nothing about .Net standard didn't mean you couldn't choose to use the giant monolith instead, it just guaranteed some semblance of stability if that was your preference.
"net5.0-windows (and later net6.0-android and net6.0-ios). These TFMs represent OS-specific flavors of .NET 5 that include net5.0 plus OS-specific functionality." Wait - net6.0- is actually net5.0?
I was surprised by this, too. I've spent the last 20 minutes researching; it seems every time I look away for more than a few minutes, Microsoft changes things up (then leaves nasty comments like didn't you read the FAQ or 'it was explained clearly, .net 5 is a separate language together and individually' https://forums.xamarin.com/discussion/177951/future-of-xamar... ). My reading of this is that Xamarin has been dr…
https://devblogs.microsoft.com/dotnet/announcing-net-5-previ...
This announcement was made in a post announcing a preview release instead of its own post, so I can see why people missed it.
Earlier articles in this ongoing series of “how to name things”: - September 2016: Introducing .NET Standard ( https://devblogs.microsoft.com/dotnet/introducing-net-standa... ) - May 2019: .NET Core is the Future of .NET ( https://devblogs.microsoft.com/dotnet/net-core-is-the-future... ) - May 2019: Introducing .NET 5 ( https://devblogs.microsoft.com/dotnet/introducing-net-5/ ) (Yes, the last two are from the same mo…
.Net framework (the same thing that MS always had)
A new named cross platform framework. Not just another .Net derivative.
And a new name for the standard. Something like the Common .Net API.
That would have pretty much eliminated all confusion.
Instead they went with
.Net Framework
.Net Core
.Net standard
.Net {version_num}