141–150 of 428 posts
Earlier quoted context omitted.
Naming it ASP.NET 5 would clash with .NET Framework ASP.NET 5 MVC, hence the ASP.NET Core 5 name.
So no excuse for .Net 6 since there was no ASP MVC 6 right?
.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.
MAUI was the big release I was looking forward to most with .NET 6, appears to be postponed.
Is there a mature(!) webview library for .NET so I can build cross-platform GUIs with HTML/JS/React but write the backend in C#/F# and bundle that whole thing into a single file (not a zip/something that gets extracted on run) for every platform?
WebView2: https://developer.microsoft.com/en-us/microsoft-edge/webview... For instance, in WPF applications: https://docs.microsoft.com/en-us/microsoft-edge/webview2/get...
As a relatively new engineer (~2 years FAANG experience), there seems to be a connotation around .NET. Perhaps this is indicative of the larger Microsoft ecosystem, but it feels like my peers at university and in the industry tend to stay far away from .NET for personal projects, etc. Why is this?
I think .NET is still seen as if it's Windows-only or Windows-first. If it does start being used cross-platform, I think it will take a lot more time to get there, especially since Java has been working just fine for the same sorts of projects. And it's an especially hard sell given that it doesn't have a good GUI situation. Support for Windows GUIs is back since .NET 5, but the cross platform options are weak. It's…
Avalonia is great and recommended by most people that used it. Or do we now only count Microsoft-made solutions and then whine that .NET is not open to OSS?
As a relatively new engineer (~2 years FAANG experience), there seems to be a connotation around .NET. Perhaps this is indicative of the larger Microsoft ecosystem, but it feels like my peers at university and in the industry tend to stay far away from .NET for personal projects, etc. Why is this?
The package manager is not the best, it may have improved since last I used it. Also .Net really needs Visual Studio (not VS Code) to unlock its full potential.
>> 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.
It requires a PhD to understand versioning at this point.
Earlier quoted context omitted.
And Entity Framework Core unfortunately because EF6 was already a thing.
Yeah, hopefully as others have pointed out, with .NET 7 next year all the version numbers align so that ASP.NET and EF can drop "Core" again.
> Supported for three years as the latest long term support (LTS) release. This is the first thing I look for in these announcements. .NET 6 is the successor to .NET Core 3.1.
Three years doesn't seem very "long".
Which is not far from say Ubuntu LTS at five years. (Python and Ruby have more confusing security fix policies than LTS/stable designations, but both are relatively close to the 3-5 year mark for security fixes.)
Definitely not "long" from the perspective of classic Enterprise development (or Windows "LTS" lengths), but from modern viewpoints it is "long". Interesting how such things shift culturally.