Welcome to the Git repo that is associated with part 3, that's chapters 12 to 17, of the the book Entity Framework Core in Action (second edition). Part 2 is called "Entity Framework Core in depth", and is the real-world applications part with events, Domain-Driven Design, performance tuning, Cosmos DB, adn unit testing.

The current release of this code is running on:

• EF Core 5.1
• ASP.NET Core 5.0 (You MUST have NET 5.0 installed)

Other branches are:

• master, which covers part 1 of the book - chapters 1 to 6.
• Part2, which covers part 3 of the book - chapters 7 to 11.

To run any of the code you need to.

1. Install a development tool, either Visual Studio or Visual Studio Code (VS Code for short). If you are new to .NET Core development, then I recommend Visual Studio - here is a link on how to install Visual Studio.
2. You need to install the NET 5 or above SDK. You can find this a Microsoft NET download - select the Build apps - SDK version.
   NOTE: If you installed the latest version of Visual Studio it should have installed NET 5 SDK for you. Use the console command dotnet --list-sdks to check what NET versions are installed.
3. You need to install a SQL Server to run any applications and some of the unit tests. A SQL Server called localdb is installed when you install Visual Studio on Windows by choosing the "Data storage and processing" feature (VS Code and Visual Studio on Mac needs more work).
4. Clone this repo to your local computer. See Visual Studio tutorial called Open a project from a repo.

I have placed all the code relating to part 3 of the book, chapters 12 to 17. The BookApp.UI, which is the ASP.NET Core application, is significancy different from Part 1 and 2. It is built using a number of different approaches such as Modular Monolith, Domain-Driven Design (DDD), and a Clean Code architecture.

The Part3 BookApp is designed to show different ways to performance tune EF Core applications and introduces you to Cosmos DB.

Once you have installed your chosen development tool you can run the BookApp, which is designed to create and seed a SQL Server database on startup. The BookApp.UI application can be run from Visual Studio or VS Code. The home page of the BookApp.UI application contains a Things to do section with links to a page telling you how to configure the BookApp.UI for chapter 15 and 16.

Every chapter has a set of unit tests to check that what I say in the book is correct. These unit tests are also useful to you the reader as sometimes seeing the actual code is a quicker way to see how something works.

The unit tests are all in the Test project and uses xUnit. The unit tests are all in the UnitTests directory split into directories based on what they are testing - for instance, the UnitTests/TestDataLayer directory have all the tests that work directly with the database.

If you are using Visual Studio, then its Test feature via the Test button found on the top toolbar - see Microsoft's VS unit test docs.

If you are using VS Code, then you use it Test feature, via the tests icon (looks like a scientific flask). VSCode needs some setting up to work with C#, but this repo has the necessary .vscode files set up to run the unit tests - see VS Code C# docs for more on using VS Code C#.

Many of the tests use SQLite in-memory databases which just work. But some tests use SQL Server. If you are using Visual Studio on Windows you should install the the "Data storage and processing" feature. This should give you a SQL Server called localdb, which the standard unit tests use. If you need to change the SQL Server name etc. then you should change the connection string called UnitTestConnection in the appsettings.json file in the Test project.

If you are using Visual Studio on Mac, or VS Code on Mac or linux, then you need to install a SQL Server to allow the unit tests that need that type of database.

If you are having problems with the application then please post an issue on the EfCoreInAction-SecondEdition issues page, with the stack trace or compile error and I will have a look and get back to you.

If you find an error in the book, then please add a comment via Manning's LiveBook version of the book. Please make sure you say what section it is in as it's sometimes hard for me to link your comment to the section of the book.