Entity Framework VS AutoFixture

* 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

Yes, it does feel like some of the "standard stuff" in other more nuanced languages are missing (especially miss AutoFixture ngl). Some of those are a conscious decison by the golang team for example.

Our first test is very easy, I like to name my tests as MethodName_GivenCondition_ShouldExpectedResult to follow the pattern, I have added GetById_GivenRecordDoesNotExist_ShouldReturnNull and I am going to leavarage excellent AutoFixture to get a new Guid as parameter. For this test we don't need arrange part, we would skip to the act and then assert. For Assertion I am going to use FluentAssertions. For this test we need to assert the returned result is null.

The next test to talk about, is that if this was a bank, we would have multiple customers, who can hold multiple accounts that we need to calculate the interest for. You could manually construct these objects if you want, but I'm going to use a package called AutoFixture to make life easier.

AutoFixture is an amazing library that simplifies the process of creating test data in .NET. If for some reason you don't use this fantastic tool, it's time to consider it. Today, I'm going to share some tips for using AutoFixture that will be beneficial for developers of all skill levels. Let's get started!

AutoFixture

Ensuring that your test is still readable and not bloated by the setup of those variables may be quite a challenge but hopefully no more with AutoFixture, let's see how!

One neat library for creating and generating test data is AutoFixture.  The creators describe it as follows:

First time I heard of Bogus, looks interesting, been using AutoFixture for those will definitely take a look at it.