practical-aspnetcore VS service-fabric

Peruse samples here https://github.com/dodyg/practical-aspnetcore

Check out this repo - https://github.com/dodyg/practical-aspnetcore/tree/net6.0/projects/security/authentication-with-identity

For example, @nitaro (idk the username) shared this GitHub project in one of the past posts that I thought would be a great place to start: https://github.com/dodyg/practical-aspnetcore/tree/net6.0/exercises/pathway-1. I usually work on projects on my own but it’s so much more helpful just having others who are doing the same thing at the same time to bounce ideas off of and get support from!

Check also the samples at https://github.com/dodyg/practical-aspnetcore. It's all tiny samples that you can try out to see some functionalities.

and I maintain a pretty popular open source project https://github.com/dodyg/practical-aspnetcore

The first on the list is the entry project .sfproj. They use a non-SDK-style project template with a bunch of .xml files for configuration but with no C# code. They require Fabric.MSBuild nuget to build and package Service Fabric apps. Unfortunately, the dotnet add package command won't update dependencies since they only support and non-SDK-style project template uses the package.config file to manage dependencies.

Proprietary in what way?

Setup your ASP.NET app as a scaleable service that can run in a distributed fashion. You may be able to use something similar to Service Fabric to help - https://github.com/microsoft/service-fabric

Considerable amount of Azure Service Fabric is written in C# https://github.com/microsoft/service-fabric. As many people mentioned already, until .NET Core, no platform developers really cared about C#. Perhaps in future we may see interesting things happen with a lot of performance optimisations coming to C# as well.