Join the DZone community and get the full member experience.
.Net 6 SDK was just released by Microsoft, and apparently it’s a really kick …
Join the DZone community and get the full member experience.. Net 6 SDK was just released by Microsoft, and apparently it’s a really kick ass upgrade. It significantly optimises Stream, reduces memory footprint, and contains tons of new cool features. Probably the most important code improvement change for me personally, is the mutable DOM classes for System. Text. Json, which over time will allow me to completely replace Newtonsoft. JSON with the builtin libraries, reducing dependencies in my core. Dependencies is a big thing for me in Magic, which I’m trying to reduce to a minimum. In fact, dependency reduction is arguably my single most important axiom for improving code quality and modularity, something I guess the fact that Magic contains 30+ projects is a testimonial towards. My experience with updating Magic to use version 6 was almost 100% painless. Basically, I did a search and replace through my.csproj file replacing « net5.0 » with « net6.0 », and everything (almost) immediately worked.1,000+ unit tests are green,125+ integration tests are green, and while manually quality assuring features in Magic after updating, I was not able to find any breaking changes at all for me personally. Of course, I am trying as much as possible to use. Net Standard as much as I can in most of these projects, but still there were 20+.csproj files that were updated during this process. Microsoft did a great job with. Net 6. Several (fake) compiler warnings simply disappeared, such as the Analyzer DLL loaded twice thing, which was a bug in the way it was consumed from one of the core. Net 5 assemblies. At least so far, I’m extremely impressed. However, the tooling space might be a bit challenging. For instance, I’m using SonarCloud on Magic, and apparently these parts are not working, something you can see on my Actions tabs in my Magic satellite projects.
