Hot Chocolate VS AspNetCore.Docs

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

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.

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.

This is not a MS project, but this thing called Hot Chocolate here (https://github.com/ChilliCream/hotchocolate) is very incredible. It is the best GraphQL framework I've worked on with excellent /EF(core)?/ support (even better than that of Hasura and dgraph) on the .NET ecosystem and overall software engineering. Maybe I can even swap the data source out with MongoDB as well, since it actually accepts IQueryable as the resolver source.

.NET is so incredibly underrated...

Popular GraphQL libraries for .NET include GraphQL.NET and Hot Chocolate. To see GraphQL in action with a Blazor WebAssembly app, follow the Get started with Strawberry Shake guide. A companion to HotChocolate (GraphQL on the server), Strawberry Shake creates .NET GraphQL client proxies to consume endpoints with strongly-typed payloads.

I found hotchocolate library which does most of the work and creates a neat GraphQL server in no time. I found its tutorial quite succinct and to-the-point, you can find it here

Certain parts of Microsoft Learn are permissive, for example the .NET BCL documentation is Creative Commons Attribution: https://github.com/dotnet/dotnet-api-docs as is ASP.NET Core: https://github.com/dotnet/AspNetCore.Docs (a good hint if documentation is permissively licensed and on GitHub is if there's an edit button at the top.)

The C# language specification is unfortunately a bit fuzzier: https://github.com/dotnet/csharplang/discussions/4855

The updated unified C# language specification is CC, but it's still catching up to modern C#: https://github.com/dotnet/csharpstandard

looks like 8.0 release? https://github.com/dotnet/AspNetCore.Docs/commit/e8ce5761969...

I am coming from .Net Framework and supporting the legacy apps to .Net Core ecosystem fairly recently, so I might have missed couple of release notes so please bear with me. In the .Net Framework usage of HttpContext outside HttpRequest was discouraged because it isn't thread safe. Now I get this feedback and then I google around a bit and I find topics like this: https://github.com/dotnet/AspNetCore.Docs/issues/18419 or like this onehttps://learn.microsoft.com/en-us/answers/questions/1143595/asp-net-core-web-api-how-to-use-user-claims-in-ser

I am not sure what you mean,but here you can find all the supported ways of accessing the httpcontext in.net core https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/fundamentals/http-context.md maybe this can help you

Whilst EF6.3 had some support (note: designer doesn’t work) in .NET Core 3.1 (sample), I’m not sure if that applies to NET6. You could certainly give it a try.

11. ASP.NET

Also this discussion https://github.com/dotnet/AspNetCore.Docs/issues/26250