asp.net-core

This is the forth (and last) post in the Integration tests in ASP.NET Core series. Part 1: Limitations of the EF Core in-memory database providers Part 2: Using docker-compose for your ASP.NET + EF Core integration tests Part 3: ASP.NET Core integration tests with docker-compose on Azure Pipelines Part 4: ASP.NET Core integration tests with docker-compose on GitHub Actions (this post) In the previous post of the series we saw how to create and run our tests in a CI fashion using Azure Pipelines....

This is the third post in the Integration tests in ASP.NET Core series. Part 1: Limitations of the EF Core in-memory database providers Part 2: Using docker-compose for your ASP.NET + EF Core integration tests Part 3: ASP.NET Core integration tests with docker-compose on Azure Pipelines (this post) Part 4: ASP.NET Core integration tests with docker-compose on GitHub Actions In the last post of the series we saw how to use SQL Server on Docker as the database for our integration tests during local development....

This is the second post in the Integration tests in ASP.NET Core series. Part 1: Limitations of the EF Core in-memory database providers Part 2: Using docker-compose for your ASP.NET + EF Core integration tests (this post) Part 3: ASP.NET Core integration tests with docker-compose on Azure Pipelines Part 4: ASP.NET Core integration tests with docker-compose on GitHub Actions In this post, we will be looking at how you can run the integration tests of an ASP....

This is the first post in the Integration tests in ASP.NET Core series. Part 1: Limitations of the EF Core in-memory database providers (this post) Part 2: Using docker-compose for your ASP.NET + EF Core integration tests Part 3: ASP.NET Core integration tests with docker-compose on Azure Pipelines Part 4: ASP.NET Core integration tests with docker-compose on GitHub Actions In this post we’ll be looking at some of the limitations you may encounter while using the EF Core in-memory database providers for your ASP....

In this post, I will share with you a solution to a problem that I see often when developing ASP.NET Core apps that use both Fluent Validation and Entity Framework (Core). I’ll first set the scene: Show the EF Core Entity + Configuration + Fluent Validation we’ll be working on. Next, I’ll show the actual problem that emerges with this approach and in the end how can it be improved/solved....