Entity Framework VS ASP.NET Core

* 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

This approach to organizing middleware enhances code readability, maintainability, and reusability. By following this encapsulation pattern, you're adhering to best practices in ASP.NET Core development, ensuring your application remains well-organized and scalable.

🌟.NET 9 Preview 2 ➡️.NET 9 Preview 2 Discussion ➡️ASP.NET Core updates in .NET 9 Preview 2 ➡️ASP.NET Core updates in .NET 9 Preview 2 Release Notes ➡️EF Core updates in .NET 9 Preview 2 ➡️.NET Aspire preview 4 - .NET Aspire

https://github.com/dotnet/aspnetcore/issues/50643

Even if you look at Microsoft’s by far most popular GitHub project, they’re still only half as big as SupaBase. If you believe “the SupaBase story”, SupaBase grew and became twice as large as Microsoft in 3 years. Below is their likes over time if you’re curious, together with a couple of additional “too good to be true” Silicon Valley projects.

https://github.com/dotnet/aspnetcore/issues/10117

To achieve these objectives, we will take inspiration from ASP.NET Core Identity's PasswordHasher class. It incorporates a concept of hash versioning, allowing only the number of iterations to be modified.

yes I watched several courses, may be aim not getting clearly. but i worked with asp.net which uses http call and firebase cloud function also which uses socket connection, for socket connection its makes sense to use observable bcoz there streams of data we can observe once the connection establish ,but for http it need to be call every time.

As I'm not utilizing ASP.NET, despite its resource-intensive nature and occasional unpredictability, I prefer the cost-free option. I'm hesitant to invest in EPPlus or engage in trials, and moreover, I am more proficient with Interop. Given the limited volume of records in my department, there's a preference for utilizing tools covered by our existing license. This avoids the need for navigating through layers of approval within the chain of command and ensures compliance with our contractual agreements and Microsoft's patch management, ultimately aligning with a cost-saving mindset.