SAEA | performance IOCP framework TCP based on dotnet standard | Websocket library

I am currently following the tutorial for eShopOnContainers, and I decided to try to test out the GRPC functionality, similar to the project.

What I am trying to build is GRPC Client and GRPC Service, which are both hosted on docker and can talk to each other. Now, I managed to make it work, and if you look a the Startup.cs in GRPC Client, this Uri http://host.docker.internal:5104 manages to make the call and get the response.

However, the original eshopOnContainers project uses the http://basket-api:81 path, which is much nicer and in my opinion more maintainable. It also uses few more components and some configuration:

1. The GRPC Service uses the following in Startup.cs:
   app.UsePathBase("/basket-api") Original project
   and some configuration in Program.cs to listen to ports:

I'm trying to use SonarCloud in my GitHub Actions builds to analyze my code and to produce code coverage for my unit tests. I'm working on a .NET 5 solution in Visual Studio 2019.

At first, I was trying the SonarCloud GitHub action (https://github.com/SonarSource/sonarcloud-github-action), but the log told me to use the SonarScanner for .NET. I've setup my workflow file following the documentation: https://docs.sonarqube.org/latest/analysis/scan/sonarscanner-for-msbuild/. I'm using the dotnet-sonarscanner global tool in the workflow.

The workflow looks like this:

What are the benefits of SocketTaskExtensions against Socket asynchronous methods using SocketAsyncEventArgs?

It's really confused about either using Socket.AcceptAsync(SocketAsyncEventArgs) or await Socket.AcceptAsync() the only difference that I can see is the not using of SocketAsyncEventArgs which reduces the single object allocation of SocketAsyncEventArgs and provides a much cleaner/less code.

Socket.AcceptAsync(SocketAsyncEventArgs)