Roslyn VS Entity Framework

.NET is a little smarter about switch code generation these days: https://github.com/dotnet/roslyn/pull/66081

Recently, while creating some experimental C# source code generators (xafero/csharp-generators), I was just concatenating strings together. Like you do, you know, if things have to go very quickly. If you have a simple use case, use a formatted multi-line string or some template library like scriban. But I searched for a way to generate more and more complicated logic easily - like for example, adding raw SQL handler methods to my pre-generated DBSet-like classes for my ADO.NET experiment. You could now say: Use Roslyn and that's really fine if you look everything up in a website like SharpLab, which shows immediately the syntax tree of our C# code.

At runtime, the Case C# expressions are embedded into a function and dynamically compiled into an assembly using the Roslyn C# compiler. Then the function that contains the expression is called (e.g. CaseAvailableFunction.Availablle()). At runtime, the function provides various methods to access stored case values as well as the current input data.

* You can check the original CreateMigration implementation at: https://github.com/dotnet/efcore/blob/release/7.0/src/EFCore.Relational/Migrations/Internal/MigrationsAssembly.cs

Since .net core came out it's possible to run and write .net code in all platforms. In your experience what is the best when it comes to development experience and resources consumption? I recently moved to Linux Mint as my daily driver and felt that .net on Windows just works better, even with Rider. I struggled with an issue "Platform not supported exception" when trying to connect with the database using EF Core and NET 6.0. A lot of issues about this matter were opened on GitHub and closed without a proper resolution and the Microsoft teams seems to not give a shit about that, most workaround came from the user's who took their time to investigate the issue.

Thanks Dave. Looks like sequelize has TypeScript support.

On another note: one of the goals of Tankman is to compile with Native AOT once .Net 8 is out. The EF Core team is working on making it compatible - https://github.com/dotnet/efcore/issues/29754

It’s a known issue in the Xamarin / .NET MAUI world. Here’s a GitHub Issue posted 5 years ago detailing the problem: https://github.com/dotnet/efcore/issues/12087

Entity Framework: Licencia MIT.

https://github.com/dotnet/efcore/issues/23291 seems like there was an issue but it has been resolved.

No they aren't. I don't know why you thought that link has anything to do with window functions. Here's the ticket in the backlog. https://github.com/dotnet/efcore/issues/12747

https://github.com/dotnet/efcore ,https://github.com/dotnet/aspnetcore , https://github.com/dotnet/maui - I've experience with developing android apps as well , may be I can contribute to this

More Info: https://github.com/dotnet/efcore/issues/19129