Stories
Slash Boxes
Comments

SoylentNews is people

posted by Fnord666 on Tuesday May 07 2019, @01:32AM   Printer-friendly
from the one-.NET-to-rule-them-all dept.

Submitted via IRC for AndyTheAbsurd

Today, we're announcing that the next release after .NET Core 3.0 will be .NET 5. This will be the next big release in the .NET family.

There will be just one .NET going forward, and you will be able to use it to target Windows, Linux, macOS, iOS, Android, tvOS, watchOS and WebAssembly and more.

We will introduce new .NET APIs, runtime capabilities and language features as part of .NET 5.

[...] We intend to release .NET 5 in November 2020, with the first preview available in the first half of 2020. It will be supported with future updates to Visual Studio 2019, Visual Studio for Mac and Visual Studio Code

Source: https://devblogs.microsoft.com/dotnet/introducing-net-5/


Original Submission

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 2) by c0lo on Tuesday May 07 2019, @09:52AM (1 child)

    by c0lo (156) Subscriber Badge on Tuesday May 07 2019, @09:52AM (#840070) Journal

    The SDK, yes. However, the topic is .Net Core, which will skip 4.0

    --
    https://www.youtube.com/watch?v=aoFiw2jMy-0 https://soylentnews.org/~MichaelDavidCrawford
    Starting Score:    1  point
    Karma-Bonus Modifier   +1  

    Total Score:   2  
  • (Score: 3, Informative) by ikanreed on Tuesday May 07 2019, @03:01PM

    by ikanreed (3164) Subscriber Badge on Tuesday May 07 2019, @03:01PM (#840199) Journal

    That's because while the compiler and platform features changed, the actual VM had no changes to support 4.0 or 4.5. All the major changes were in "high level" functionality. Things like async and await were built on existing multithreading libraries. To a developer, they were real features, but to the VM it was indistinguishable from pushing task objects onto threadpools.