.NET Standard 2.1
blogs.msdn.microsoft.com
.NET Standard 2.1
1–10 of 124 posts
Re: .NET Standard 2.1
#2I actually don't care very much if they're actually the same code base, but I'd like to be able to use the dotnet CLI for everything. Xamarin project templates in the new SDK format are also on my wishlist.
Re: .NET Standard 2.1
#3Anybody got any updates on the state of Mono/.NET Core convergence? I actually don't care very much if they're actually the same code base, but I'd like to be able to use the dotnet CLI for everything. Xamarin project templates in the new SDK format are also on my wishlist.
Re: .NET Standard 2.1
#4At some point, is it reasonable to expect Xamarin, Mono, Unity, and .NET Core to all really be backed by .NET Core? And if/when so, is there any difference between .NET Standard and .NET Core since, after .NET Framework has been essentially maintenance-mode'd, there will be only one .NET Standard implementation? Similar question, besides just having multiple implementations, what benefit is there to having both Mono and .NET Core separate (at least for the .NET Standard impl part)?
Re: .NET Standard 2.1
#5Anybody got any updates on the state of Mono/.NET Core convergence? I actually don't care very much if they're actually the same code base, but I'd like to be able to use the dotnet CLI for everything. Xamarin project templates in the new SDK format are also on my wishlist.
Are .NET Core and Mono converging? I would have thought that they'd remain separate while both implementing .NET Standard, and becoming interchangeable as .NET Standard implementations.
And here's a more recent update: https://www.mono-project.com/docs/about-mono/releases/5.0.0/...
Re: .NET Standard 2.1
#6Anybody got any updates on the state of Mono/.NET Core convergence? I actually don't care very much if they're actually the same code base, but I'd like to be able to use the dotnet CLI for everything. Xamarin project templates in the new SDK format are also on my wishlist.
Are .NET Core and Mono converging? I would have thought that they'd remain separate while both implementing .NET Standard, and becoming interchangeable as .NET Standard implementations.
Re: .NET Standard 2.1
#7- .Net Framework: The Windows Specific (and nearly deprecated) branch
- .Net Core: The replacement for Framework and cross platform branch (but with Windows specific libraries)
- .Net Standard: A way to write something that runs on both .Net Framework and Core?
Re: .NET Standard 2.1
#8Let me just check if I finally understand this: - .Net Framework: The Windows Specific (and nearly deprecated) branch - .Net Core: The replacement for Framework and cross platform branch (but with Windows specific libraries) - .Net Standard: A way to write something that runs on both .Net Framework and Core?
Re: .NET Standard 2.1
#9> Given many of the API additions in .NET Standard 2.1 require runtime changes in order to be meaningful, .NET Framework 4.8 will remain on .NET Standard 2.0 rather than implement .NET Standard 2.1. .NET Core 3.0 as well as upcoming versions of Xamarin, Mono, and Unity will be updated to implement .NET Standard 2.1. At some point, is it reasonable to expect Xamarin, Mono, Unity, and .NET Core to all really be backed…
https://docs.microsoft.com/en-us/dotnet/standard/net-standar...
Re: .NET Standard 2.1
#10- .Net API Specification - (now known as .Net Standard)
- .Net Windows - (now known as .Net Framework)
- .Net Cross Platform - (now known as .Net Core)