Blazor.IndexedDB.Framework VS Entity Framework

Blazor WASM was the first, original version. I wanted an app that can work offline, so I decided to save user data in IndexedDB. My first choice for an IndexedDB NuGet was https://github.com/Reshiru/Blazor.IndexedDB.Framework because it was recommended by Steve Sanderson in https://blog.stevensanderson.com/2019/08/03/blazor-indexeddb/ - and it was the worst mistake in the whole project. The NuGet loads all the data from IndexedDB into memory every time you open a connection. That made the app unusably slow after one year of use. I made a few improvements in my own version https://github.com/Jinjinov/IndexedDB.Blazor but I never solved the loading problem. I decided to rewrite the whole project from scratch, using the much better IndexedDB NuGet https://github.com/amuste/DnetIndexedDb . The original project is available at https://github.com/Jinjinov/TheLastTime and as a PWA https://old.ididit.today/ as a lesson on what mistakes to avoid.

https://github.com/Reshiru/Blazor.IndexedDB.Framework - 67 stars - 1 contributor - last commit on Jan 26, 2021 - uses https://github.com/wtulloch/Blazor.IndexedDB - archived

* 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