For me Hot Reload is the most important feature, which will very likely be a reason for me to move a bit from Python over to .NET, which I haven't touched for 10 years. Back then I really used it a lot (after moving away from OLE/DCOM/ActiveX), in C++, Managed C++, C# and IronPython (no GIL!). I absolutely loved it, but it was limited to the Microsoft ecosystem.<p>Yesterday, while randomly googling for "hot reload" I got aware of the drama which went down around two weeks ago, when Microsoft decided to remove this feature from the release, even after including it in the previews.<p>Here is a good summary <a href="https://www.youtube.com/watch?v=L9_pzDjw9HQ" rel="nofollow">https://www.youtube.com/watch?v=L9_pzDjw9HQ</a>
> In .NET 6, in-memory single file apps have been enabled for Windows and macOS. In .NET 5, this deployment type was limited to Linux. You can now publish a single-file binary that is both deployed and launched as a single file, for all supported OSes. Single files apps no longer extract any core runtime assemblies to temporary directories.<p>This is a great! Now I can publish statically linked executables and run it everywhere. I don't have to tolerate Golang and its quirks just to have cross-compilation and static binaries, even though they will be larger in size.
.NET 6 seems like a pretty good release with a few cool new features.<p>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.
> Supported for three years as the latest long term support (LTS) release.<p>This is the first thing I look for in these announcements. .NET 6 is the successor to .NET Core 3.1.
> System.Linq — DistinctBy/UnionBy/IntersectBy/ExceptBy<p>I'm excited by having these built in. I always found it awkward to need to do: `.GroupBy(item => item.Property).Select(group => group.First())`.
Is there any reason I should care about .NET today if I'm not already in the ecosystem? I've done C# professionally in the past, and C# is a good language. I wish Microsoft focused on open source and wider industry adoption for C#/.NET sooner so that it could have taken some share from Java. Now .NET is finally open source but Microsoft is a bad steward of the open source ecosystem for .NET, and I certainly wouldn't feel comfortable to say to my team "let's do this next project in C#". I don't see any particular reason to make my own tools in C# vs anything else.<p>So without already being in an existing Windows-based Microsoft shop, is there any reason I should be interested in .NET today?
>> ASP.NET Core in .NET 6.<p>I've been on .net since 1.1 and .net Core since 1.0 and this statement makes me so confused.<p>Core lives _inside_ of .net 6? Is there a non-core ASP.NET that also lives inside that framework?<p>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.
As a relatively new engineer (~2 years FAANG experience), there seems to be a connotation around .NET.<p>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.<p>Why is this?
We recently got through upgrading a large code base from .NET framework to .NET core 3.1. It was quite challenging as it seemed to touch every corner of .NET including AppDomains, .NET remoting, serializing type information, C++ interop which requires environment variables to be set in process (that one is very obscure), etc, etc.<p>In any case, the performance results were really outstanding (particularly vs Mono) especially given we use C++ for many performance sensitive areas already. Looking forward to upgrading to .NET 6 in the coming months.<p>Great work! Congrats to the .NET team!
I 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.<p>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.<p>MS are starting to feel like Apple where you only have value if you can keep up.
Been thinking about switching to Rider (already had the personal license for Jetbrains from wanting CLion for Rust) and figured .NET 6 would be a good time to try making the switch. With how blah VS has been for a while hopefully I'll like the Rider experience better (for both c# and f#)<p>Edit: Though I saw something this morning when I tried to load an f# project I made in VS refused to load even though the new ones generated with Rider are fine...
.NET seems to be getting better every year. Really interested to learn and use it for daily basis.<p>I just wished more startup are using it more as their tech stack to improve the ecosystem to be on par with Java. Almost every big tech companies are always using java now it's just hard to use .net when you won't get a job that doesn't suck
Java user here. What is a good book/set of resources on getting started in .NET/C#, possibly this version 6, without knowing the ecosystem beforehand (but with a experience in programming)? Thanks!
I moved from C# to the NodeJs/JS/React world a while ago, when React was fairly new as well.<p>I like JS as a language and the enormous progress thats been made in the JS ecosystem from the wild west days back then. But I have to say my most productive and enjoyable dev experience was with VS, C#, ReSharper etc.<p>Magical intellisense and real refactoring across millions of LOCs and multiple assemblies, all kinds of tools, visual designers, powerful 3rd party toolkits (anyone remember Infragistics), amazing docs. And of course now it'd be much better I'm sure.
> .NET 6 is the first release that natively supports Apple Silicon (Arm64)<p>Finally! :)<p>I was a bit disappointed that MS didn’t want to support macOS arm64 natively with .NET 5.<p>At the same time Microsoft invested a lot of effort in porting Java to arm64. Almost a year ago I could download Java builds for macOS arm64 from Azul (java 8-latest).
Is it possible to load ".NET Framework" assemblies into ".NET 6" applications?<p>(We have a lot of .NET Framework libraries, shared between different applications, and a complex dependency graph between them. So I'm wondering if it is possible to migrate away from .NET Framework by starting with the executables and working our way down the dependency graph.)
Fast framework for Web, MAUI for mobile and desktop, Blazor for frontend, ML.NET for AI and ML, Unity and Godot for games, F# for functional programming. All relatively fast and easy to use. Libraries for everything and good documentation.<p>The only thing we miss is system programming due to not being able to opt out of using the garbage colector.
this is nice.<p>I built a couple of side-projects and startups - all on .net.<p>First one was on Xamarin even before it was bought by MS - the progress from that times is amazing, the last one - built fully on Blazor.<p>I believe more startups should try to adopt .net stack - it's fast, fun and efficient and becomes better every day.<p>Congrats .net teams on launch
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?
.NET 6 was released but MAUI was pushed for next year and I still haven't heard anything about AOT which was delayed a few times and was supposed to come WITH .NET 6.
Unlike all the preview builds this actually crashed on `dotnet run` after upgrading. Luckily a `dotnet clean` fixes it.<p>Good to finally have an official version!