.NET 6 Released
devblogs.microsoft.com
.NET 6 Released
1–10 of 428 posts
Re: .NET 6 Released
#2Unlike all the preview builds this actually crashed on `dotnet run` after upgrading. Luckily a `dotnet clean` fixes it.
Good to finally have an official version!
Re: .NET 6 Released
#3I would personally prefer you to fix the multitude of things that don't work well in Visual Studio and library issues that are continually pushed back as "won't fix" or "upgrade to .Net5/6" as opposed to always racing forwards to the horizon.
Even those of us who are actively migrating applications are stuck with web forms, netfx and dotnet core 2/3 and will be for years, so it would be nice that we felt some love rather than being left behind.
MS are starting to feel like Apple where you only have value if you can keep up.
Re: .NET 6 Released
#4>> ASP.NET Core in .NET 6.
I've been on .net since 1.1 and .net Core since 1.0 and this statement makes me so confused.
Core lives _inside_ of .net 6? Is there a non-core ASP.NET that also lives inside that framework?
I thought .net 5 was where the legacy 4.x branch and core 3.1 was married in holy matrimony, minus the worst of the legacy garbage.
Re: .NET 6 Released
#5.NET 6 seems like a pretty good release with a few cool new features.
But it's funny how the infographic in the post mentions MAUI for desktop development, but the "desktop" keyword in the text is referring to the WinForms github repository. I can't think of a more concise statement about the state of GUI development on .NET. I would really wish for less fragmentation and churn in that space.
Re: .NET 6 Released
#6MAUI was the big release I was looking forward to most with .NET 6, appears to be postponed.
Re: .NET 6 Released
#7>> ASP.NET Core in .NET 6. I've been on .net since 1.1 and .net Core since 1.0 and this statement makes me so confused. Core lives _inside_ of .net 6? Is there a non-core ASP.NET that also lives inside that framework? I thought .net 5 was where the legacy 4.x branch and core 3.1 was married in holy matrimony, minus the worst of the legacy garbage.
I think "ASP.NET" would imply the legacy web framework, so they had to keep the "ASP.NET Core" name. Not unlike EntityFramework & Entity Framework Core.
Re: .NET 6 Released
#8>> ASP.NET Core in .NET 6. I've been on .net since 1.1 and .net Core since 1.0 and this statement makes me so confused. Core lives _inside_ of .net 6? Is there a non-core ASP.NET that also lives inside that framework? I thought .net 5 was where the legacy 4.x branch and core 3.1 was married in holy matrimony, minus the worst of the legacy garbage.
Naming it ASP.NET 5 would clash with .NET Framework ASP.NET 5 MVC, hence the ASP.NET Core 5 name.
Re: .NET 6 Released
#9I would personally prefer you to fix the multitude of things that don't work well in Visual Studio and library issues that are continually pushed back as "won't fix" or "upgrade to .Net5/6" as opposed to always racing forwards to the horizon. Even those of us who are actively migrating applications are stuck with web forms, netfx and dotnet core 2/3 and will be for years, so it would be nice that we felt some love ra…
Nobody gets promoted for fixing bugs.
Re: .NET 6 Released
#10>> ASP.NET Core in .NET 6. I've been on .net since 1.1 and .net Core since 1.0 and this statement makes me so confused. Core lives _inside_ of .net 6? Is there a non-core ASP.NET that also lives inside that framework? I thought .net 5 was where the legacy 4.x branch and core 3.1 was married in holy matrimony, minus the worst of the legacy garbage.
.NET is sane now... .NET 5, .NET 6, .NET 7... all cool, no more confusion going forward...
.NET Framework(full Windows only Framework) is .NET Framework 4.x, stuck there forever only security patches...
Only remaining confusing part left in ecosystem is "ASP.NET Core", because even though .NET got rid of Core, latest version ASP.NET didn't