Project complexity, for its own sake, bites back.
Introduction and Background
I was going to write a follow up of my article “Setting up Entity Framework in an MVC .Net Core project,” showing how easy it is to connect the MVC controllers and pages to the Entity Framework database and classes. If I were satisfied with showing code that worked but had ugly hidden bugs and traps embedded in the structure, I could have had that written and published Friday. But no, I have to be ethical and work out what my bugs are before I give examples. So, I can’t show you how easy it is to do, because there were some subtle problems with the underlying framework I had built.
Interestingly enough, it has little to do with the Entity Framework classes I talked about in that last article. There are some subtle missing parts of the project. The first mistakes I made were in initially configuring the Entity Framework model and the structure of the NuGet Packages. Going back to my article “Private NuGet Packages,” the article wasn’t wrong, but I wasn’t clear enough on the implications. I am going to correct that mistake, along with talking about some of the limits of even what appears to be a well-written Test set for complex data-driven user-interactive projects.
Setting the background just a bit, I have my star system database with a simple web front-end that…
