Aram Koukia

.NET Core 2.0 is around the corner, and it’s gonna be huuuuge!

I’m very excited about the .Net Core 2.0 release. It reminds me of .Net Framework 2.0 release (around 2001 I guess! getting old, eh?), when…

Aram Koukia 2 min read

.NET Core 2.0 is around the corner, and it’s gonna be huuuuge!

I’m very excited about the .Net Core 2.0 release. It reminds me of .Net Framework 2.0 release (around 2001 I guess! getting old, eh?), when .Net Framework 1.0 and 1.1 was release but it wasn’t great, and still people really wanted to use them so badly (Primarily because they wanted to step away from VB 6.0 development) and for sure .Net Framework 2.0 was a big move and a big milestone.

I feel the same way about this release. I think it is going to be Huuuuge!

Just to give you a sense of the changes in this release, the number of the APIs compared to .Net Core 1.1 has been doubled!

So if you are as excited and got some time to give back to the community, go head and help with the ZBB on github:

Announcement: Driving towards zero 2.0 bugs by May 10 (ZBB) · Issue #17619 · dotnet/corefx
As we are getting closer to .NET Core 2.0 Preview and .NET Standard 2.0 Preview ship dates, we would like to drive 2.0…github.com

How can you, the CoreFX contributors, help?

  1. If you’re picking up issues to work on, prefer issues marked as 2.0.0 bugs (some are even up-for-grabs).
  2. If you spot something in Future milestone that should be part of 2.0, please say so and explain why (loop in @karelz). Conversely if there’s something in 2.0 that perhaps is not as significant as it seems.
  • We strive to deliver high-quality product, so impactful bugs, compatibility, reliability and performance issues are top priority. Migration to .NET Core 2.0 from .NET Core 1.1 or from .NET Framework is one of the key priorities.
  • Adding additional new APIs, fixing pre-existing bugs or fixing corner-case issues with lower impact and with existing workaround is lower priority, not tracked as 2.0.
  1. Issues with no milestone — we expect to set their milestone in upcoming weeks (part of ongoing “triage”), so if you see something must-have for 2.0 there, please say so and explain why (loop in @karelz).
  2. Watch for upcoming official preview announcements (on .NET blog or on dotnet/Announcements repo) to help validate and dogfood the end-to-end .NET Core 2.0 experience before final release.

.Net Core Roadmap:

You can check out the .Net Core road map in details and see what’s coming up in this release in the following link:

https://github.com/dotnet/core/blob/master/roadmap.md

Cheers!