Live data from Hacker News

Performance Improvements in .NET 6

devblogs.microsoft.com

101–110 of 256 posts

Re: Performance Improvements in .NET 6

#101
post #23
post #11

Earlier quoted context omitted.

What are some of the libraries you're thinking of?

I'd like to see them to roll their own identity platform after IdentityServer went close source.

.NET already has an identity platform (ASP.NET Identity) that provides authentication/authorization with various backends. IdentityServer is a token server that speaks OAuth/OIDC and provides federation to other user directories (ASP.NET Identity or Azure Directory or anything else).

IdentityServer4 is still open-source and available. There's a new version by Duende with commercial licensing, or various alternatives like OpenIddict [1]. OAuth/OIDC is a well-supported standard so you can also use servers in other languages like Ory [2].

Microsoft's team did consider making their own token server but there was considerable pushback from the community because it would have a negative effect on open-source, and wouldn't add anything new compared to existing projects while taking resources from other framework features.

1. https://github.com/openiddict/openiddict-core 2. https://www.ory.sh/open-source

Re: Performance Improvements in .NET 6

#102
post #95

I'm going to pile in too late and sing the virtues of .NET core or whatever its called now. Deployment of web apps to containers is a breeze, the language is modern feeling. Roslyn is about the most awesome thing I have played with. Razor pages are a breeze compared to the giant piles of dependency hell that client side SPAs or node have become. It feels lean and mean and I can be sitting at a debian box or a windows…

Maui is built on top of UWP, in what concerns Windows backend. Have to agree with the desktop development chaos, look like not wanting to take an hard decision. Forms and WPF continue, because they are the golden eggs, the ones that most .NET desktop devs actually care about. WinUI looks like last attempt to rescue UWP, while at the same time in typical Microsoft fashion ignoring the tooling issues surrounding .NET N…

I think React has shown how UIs can be done in a better way. That's why we have Flutter, Jetpack Compose and SwiftUI now.

Re: Performance Improvements in .NET 6

#103
On the topic of WPF apps in .NET core:

Can anyone who has successfully migrated WPF apps to .NET core, in production, chime in on what was the experience like? Any major pitfalls or pros/cons to consider?

I have a prospective client, running a WPF app in a soon to be deprecated windows embedded machine. They have a lot of domain knowledge in the app so are unwilling to re-write or port.

I was thinking if it is feasible at all to migrate this WPF app to .NET core and then migrating the target to a higher longevity Linux machine.

Re: Performance Improvements in .NET 6

#104
post #59

Earlier quoted context omitted.

I like the uniformity of Java language. I like the "inner class" feature that has to be manually emulated in C#. I also like that I can implement anonymous abstract class-interface ad hoc in Java. I wish that internal visibility in C# was tied to a namespace instead of assembly, like package visibility in Java. Method co-/contravariance in C# is tied to interfaces. I prefer it tied to individual methods, like in Java…

>In C# it can be overloaded. I know it only confirms your point, but Rider highlights the overloaded operators so you spot them right away. After working with dotnet for pretty long time and coming to Java world (mostly Spring with Kotlin), I was extremely disappointed to find there's no real alternative to LINQ. What's your solution to this common problem: you have a table (HTML table) with 30 different filters, you…

> With LINQ and EF, it's very easy to do

I know of LINQ, but what's EF?

Re: Performance Improvements in .NET 6

#105

Where should someone start if they wanted to get familiar and proficient with .NET?

Hi, I'm on the .NET community team. Here's what we see as the happy path for .NET: - .NET website ( https://dot.net ) - High level info on different workloads, 5 minute in-browser tutorials, links to live shows and community - MS Learn ( https://aka.ms/mslearn-dotnet ) - Interactive tutorials with learning paths built from 30ish minute learning tutorials - Docs ( https://aka.ms/msdocs-dotnet ) - More in-depth documen…

Hey, thanks for your work, love .NET.

I guess this is as good of a chance as I'm gonna get - the docs experience in non-anglosphere countries is dreadful, the website keeps pushing a localized version with absolutely garbled machine translations which are never going to be even passable for technical documentation. It's just a completely miserable experience without the "FFS MSDN" browser extension.[1][2]

At least that was the situation a year or so ago - all my computers are now 100% English locale so I have no quick way to check.

Just let us use the website in English.

[1]: https://addons.mozilla.org/en-US/firefox/addon/ffs-msdn-in-e...

[2]: https://chrome.google.com/webstore/detail/ffs-msdn-in-englis...

Re: Performance Improvements in .NET 6

#106
post #48

Earlier quoted context omitted.

That's definitely true but they did a good job supporting their tech once it was released. My company has been using WinForms on .NET Framework for over 10 years now and it's working really, really well. Microsoft even added HiDPI support to it. When Microsoft announced they wanted to bring WinForms to .NET Core 3, we were initially very happy as it meant we could switch to .NET Core. But then they did all kinds of s…

No they didn't. Take a look at what happened to silverlight or UWP. You just happen to be working in the one tech they actually carried on supporting.

UWP is still supported, that is what WinUI is built on.

The problem is that they now seem to somehow carrying that flag forward on top of XAML Islands, with an endless list of bugs.

Re: Performance Improvements in .NET 6

#107
post #39

WinForms and its Visual Studio designer are still broken, WPF is still riddled with bugs and was declared obsolete in ~2017 in favor of UWP, UWP is marked obsolete in favor of WinUI, and WinUI's OSS release was postponed just two days ago because it's not ready. Microsoft is marketing .NET 6 as the replacement for .NET Framework but you still cannot properly do desktop UI with it. I honestly don't understand why they…

As far as UI in .NET in general goes they seem to be throwing stuff at the wall to see what sticks, and no one project seems to have a lot of resources dedicated to it. I imagine this is because it’s simply not a priority for the .NET team. Maybe it’s undervalued a bit, or maybe it’s making the best with the resources they have.

Re: Performance Improvements in .NET 6

#108
post #39

WinForms and its Visual Studio designer are still broken, WPF is still riddled with bugs and was declared obsolete in ~2017 in favor of UWP, UWP is marked obsolete in favor of WinUI, and WinUI's OSS release was postponed just two days ago because it's not ready. Microsoft is marketing .NET 6 as the replacement for .NET Framework but you still cannot properly do desktop UI with it. I honestly don't understand why they…

"Azure, Azure, Azure!" is the new "Developers, Developers, Developers!". Microsoft is going to focus where the business growth is, and I'm guessing they don't see improving desktop development as a big money maker for them.

Re: Performance Improvements in .NET 6

#109
post #104

Earlier quoted context omitted.

>In C# it can be overloaded. I know it only confirms your point, but Rider highlights the overloaded operators so you spot them right away. After working with dotnet for pretty long time and coming to Java world (mostly Spring with Kotlin), I was extremely disappointed to find there's no real alternative to LINQ. What's your solution to this common problem: you have a table (HTML table) with 30 different filters, you…

> With LINQ and EF, it's very easy to do I know of LINQ, but what's EF?

EF is ORM, basically wrapper over communication with database

It really, really speeds up the work, but there's a lot of to learn about how does it work, its limitations and conventions

Re: Performance Improvements in .NET 6

#110
post #48

Earlier quoted context omitted.

That's definitely true but they did a good job supporting their tech once it was released. My company has been using WinForms on .NET Framework for over 10 years now and it's working really, really well. Microsoft even added HiDPI support to it. When Microsoft announced they wanted to bring WinForms to .NET Core 3, we were initially very happy as it meant we could switch to .NET Core. But then they did all kinds of s…

> My company has been using WinForms on .NET Framework for over 10 years now and it's working really, really well. Despite WPF being preferred amongst developers, WinForms solves most use-cases well. I’ve not really kept up with Microsoft UI developments but I’d be interested in seeing any cross-platform UI toolkits they develop now or in the future just as an alternative to gtk/qt

The problem is that many features in Forms like data binding or layouts, have bugs, which happen to be only fixed on WPF, because that was the new boy in town.

So when you move beyond VB6 style of applications, there are several head scratching moments.

Post reply on HN