Moq VS Entity Framework

In terms of mocking there are several frameworks you can use, but I've mainly relied on Moq and NSubstitute. Within this demo, I'm going to use NSubstitute as I've found it a little easier to use.

Or you just run into bullshit like https://github.com/Moq/moq4/issues/173

Now to the real benefit of DI: If you are testing a method in your application that calls the ReservationRepository.GetReservation() method, you can use a library like Moq to simply "mock" a class that uses the IReservationRepository interface and define the return result of the GetReservation() method. Pass the mocked class into the constructor of the class you are testing.

MOQ https://github.com/moq/moq4

Moq

Both projects use similar testing infrastructure. I write unit tests in C# using XUnit.net. I frequently use mock objects in testing, and MOQ is my tool of choice. I utilize continuous testing and coverage analysis through Rider. I do not have specific objectives for code coverage. When writing complicated algorithms, I frequently shoot for 100% coverage of the algorithm. I test simple properties inconsistently, and frequently do not test guard clauses.

🔗 Moq documentation | GitHub

But the reality is that I don't really write my tests with it. Toss on the MSTest attributes as needed of course. But all the testing code itself is FluentAssertions with a bit of Moq. (Though I find rarely need to use Moq/mocking anymore -- scandalous, I know.)

Moq tutorial

* 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