AspNetCoreDiagnosticScenarios VS Hot Chocolate

This one is a pretty decent guide - https://github.com/davidfowl/AspNetCoreDiagnosticScenarios/blob/master/AsyncGuidance.md

The C# (mostly applicat community has e.g. https://github.com/davidfowl/AspNetCoreDiagnosticScenarios/blob/master/AsyncGuidance.md written by one of the Asp.Net architects. I found this in this lovely thread https://news.ycombinator.com/item?id=36785691 which expresses my views/confusion more clearly than I can express.

No it doesn't, hence why there are best practices guidelines written by the .NET architects, and there was a research project to add Go/Java co-routines as well.

https://github.com/davidfowl/AspNetCoreDiagnosticScenarios/b...

https://twitter.com/davidfowl/status/1532880744732758018?lan...

https://github.com/dotnet/runtimelab/issues/2057

https://github.com/dotnet/runtimelab/issues/2398

They don't work just fine in C#, there is a reason why one of ASP.NET architects has written a guide of best practices.

https://github.com/davidfowl/AspNetCoreDiagnosticScenarios/b...

Many that praise async/await in C#, kind of forget it took about 10 years to spread across all the layer of the language and runtime, since it was done via IL rewriting, it caused several issues with F# async tasks, due to the age of the ecosystem plenty of code isn't async/await friendly and needs to be wrapped into Task.Run() or similar.

There is a best practices guideline from one of the ASP.NET architects, https://github.com/davidfowl/AspNetCoreDiagnosticScenarios/b...

During last year they researched adding Go/Java's approach to .NET, but now it is too late. See the ASP.NET Q&A session at BUILD 2023.

The best guidance I have found was from here: AsyncGuidance.md

To expand upon this thought, here is the AsyncGuidance doc[1] on why not to use .Result to get the return value of a completed Task in C#.

To make this simple they introduced async Main[2] a few years ago.

[1]: https://github.com/davidfowl/AspNetCoreDiagnosticScenarios/b...

Async Guidance

have a look here https://youtu.be/qrh97hToWpM https://chillicream.com/

There are some libraries which allows you to declare some class with more or less arbitrary methods which will be called by it at runtime. I believe many of them do that in optimal way, not just using usual reflection. One of the examples is HotChocolate library https://github.com/ChilliCream/hotchocolate . You declare class with arbitrary methods which contain arbitrary arguments. "Arbitrary" doesn mean arbitrary at all, but if parameter type is registered in DI or marked by specific attribute, it can be passed to the method.

At work we are considering using GraphQL to build our read-only data-APIs using .NET 6, EF Core and SQL Server. Looking at the ecosystem the most relevant plattforms seems to be graphql-dotnet and ChilliCream.

I'm starting a brand new project. Looks like if we want to do GraphQL in .NET, it's either graphql-dotnet or Hot Chocolate. Both look pretty good on paper.

If you know it better: Please try statically typed generated graphql queries in C# (like write the graphql queries, have a graphql schema, then get generated C# types which resemble the query, the only thing I've found that could do it was https://chillicream.com/docs/strawberryshake and there I quickly hit this bug with super simple queries containing unions: https://github.com/ChilliCream/hotchocolate/issues/4662

If you don't know Hot Chocolate framework, feel free to read about it on chillicream.com (official website) and feel free to join the great community (which is always willing to help) on slack

I love using Hot Chocolate in C# ❤

Hotchocolate GraphQL server. This is the most advanced server for a .Net environment. This article does not go into the basics and assumes some framework knowledge.

I think for the time being that's the case, yeah. I'm confirming with the great people over at https://github.com/ChilliCream/hotchocolate to see if we can somehow work around that.