On July 23rd, 2019, a couple of weeks back, Microsoft announced .Net Core 3.0 Preview 7. You can download it here. It consists of new features that are an upgradation of the previous release. In the next few releases, you can expect Microsoft to focus its attention on quality. To create high-quality web solutions, contact a professional .Net development company that can aid you with supreme .Net application development services.
You can use this new version on Windows, Linux, and macOS. On top of this, ASP.Net Core and EF Core have also released their respective updates on the same day. In case you are employing Visual Studio, you will need Visual Studio 2019 16.3 Preview 1 to effectively utilize .NET Core 3.0 Preview 7.
Even the Microsoft .NET Site has been upgraded to meet the compatability of .NET Core 3.0 Preview 7. You can successfully run it on Preview 7 for more than two weeks on Azure Webapps in the form of a self-contained app. You will see the site being transitioned to Preview 8 build in a few weeks’ time.
In case you missed out on the enhancements released in .NET Core 3.0 Preview 6, click here. Also, check out June Update on WPF, here. Both of these are updates from June 2019.
Microsoft comprehensively supports .NET Core 3.0 Preview 7. You can utilize it in the production phase. But, we recommend you to test your app while running on preview 7 before deploying it into production. In case there is any issue with .Net Core 3.0, please contact Microsoft support or file a Github issue.
Some changes are anticipated after preview 7 for most APIs. Some of the noteworthy exceptions are Entity Framework, Windows Forms, Blazor, and WPF. Microsoft is still working on the compatibility with .Net Core 1.x and 2.x apps. You can now directly upgrade existing apps to .Net Core 3.0.
As far as the size is concerned, the .NET Core SDK is comparatively smaller than .NET Core 3.0. The reason for that is the way it has been constructed has undergone a drastic change. In the latest version, it uses purpose-built “packs” of different kinds. These include frameworks, reference
assemblies, and templates. While in the previous version, i.e., .NET Core 2.2, the SDK was constructed from NuGet packages. This encompassed various artifacts that were not essential, resulting in wastage of lots of space.
NET Core 3.0 SDK Size (size change in brackets)
As you can see from the chart provided above, the size enhancements for Linux and macOS are massive. On the contrary, the enhancement for Windows is smaller. The reason for that is, it has integrated Windows Forms and WPF as a part of .NET Core 3.0. Also, its installer is smaller compared to the other two.
The same benefits can be observed with .NET Core SDK Docker images. In the below-mentioned chart, it is limited to x64 Debian and Alpine.