Announcing .NET Core 3.0 Preview 8
Today, we are announcing .NET Core 3.0 Preview 8. Just like with Preview 7, we’ve focused on polishing .NET Core 3.0 for a final release and are not adding new features. If these final previews seem anti-climatic, that’s by design.
Download .NET Core 3.0 Preview 8 right now on Windows, macOS and Linux.
ASP.NET Core and EF Core are also releasing updates today.
The Microsoft .NET Site has been updated to .NET Core 3.0 Preview 8 (see the .NET Core runtime version in the footer text). It’s been running successfully on Preview 8 for over two weeks, on Azure WebApps (as a self-contained app). We will move the site to Preview 9 builds shortly.
If you missed it, check out the improvements we released in .NET Core 3.0 Preview 7, from last month.
NET Core 3.0 Preview 8 is supported by Microsoft and can be used in production. We strongly recommend that you test your app running on Preview 8 before deploying Preview 8 into production. If you find an issue with .NET Core 3.0, please file a GitHub issue and/or contact Microsoft support.
The .NET Core 3.0 release is coming close to completion, and the team is solely focused on stability and reliability now that we’re no longer building new features. Please tell us about any issues you find, ideally as quickly as possible. We want to get as many fixes in as possible before we ship the final 3.0 release.
If you install daily builds, please read an important PSA on .NET Core master branches.
Forgot to mention Visual Studio 2019 16.3 Preview 2?
Is there any VS2019 update?
Visual Studio 2019 16.3 Preview 2
Okay fine thanks..
1) Does this preview support building C++/CLI projects for Windows?
2) Does x64 .NET Core SDK installer already includes x86 or I need to install both on x64 machine? The same question for .NET Core runtimes.
3) Is .Net Core supposed to be used in offline (disconnected) scenarios? Because for now it’s impossible to compile template Windows Forms App (.NET Core) with Visual Studio 2019 Professional 16.3 preview 2 and .NET Core 3-preview8 if PC cannot reach nuget.org – https://developercommunity.visualstudio.com/content/problem/519562/cannot-compile-template-winforms-desktop-applicati.html
Checking the .NET Core Libraries Source Code by the PVS-Studio Static Analyzer: https://www.viva64.com/en/b/0656/
Does ‘Microsoft .NET Site’ use EntityFrameworkCore3.0? I’ll be happy to see it production-ready, but unluckily it is not. Problems emerge on any query that is a bit more complex than elementary. I’m a little bit dissapointed to see preview8 that hasn’t fixed issues brought with preview7 re-design. Although I understand that efcore,aspnetcore,etc aren’t literally parts of corefx, however they have same version-numbering and I suppose scheduling. Looking forward to see EFCore-preview9
Why there is no Docker image for dotnet/core/runtime-deps:3.0-alpine3.9-arm32v7 ?
What boards are supported in .NET Core 3.0 for GPIO, I2C, SPI, etc usage?
How come that you state the Preview is ready for production, when it is known that betas, previews and even release candidates are not to be used for critical applications? Even on the download site for this specific preview, the one can read (once yellow preview-tag is clicked) following:
”Preview releases provide early access to features that are currently under development. These releases are generally not supported for production use.”
“Generally not supported for production use” is exactly the reason the author stated that Preview 8 IS supported by Microsoft. There are no obligations that people should use Preview 8 if they are really concerned about anything.
It’s still a nightmare to deploy to azure, almost giving up, as Framework dependent nor Self-Contained are working for me in preview 8, and as we have our production env in Azure, this is like a huge pain….
Don’t give up!I managed to deploy it to azure, as self-contained, preview 7.
Tonight i will update to 8 but it’s only minor changes for the little app i used.
I’m using it for server-side blazor:https://github.com/MACEL94/BlazorPongLast deploy failed because i exceeded azure free tier limits but it does work, i hope u find it useful.
So far I’ve got nothing but crickets on this ASP.NET Core 3.0 question:
Is that because I’m being ignorant? Or is it because there’s no good answer yet? Probably the former! But can someone educate me a bit on this?