Ah, the dreaded package is missing the required nuspec file> build error. This happens so infrequently that when it does I don`t remember what I did to fix it last time. Well today I was testing my custom NuGet packages in an ASP.NET Core application where I had refactored out the authentication pieces into these reusable packages when I encountered this error. This time I decided to document it and add it to my blog entries for the next time this occurs for us.

On the surface, Continuous Integration (CI) and Continuous Deployment (CD) sounds wonderful, but there are a lot of things that should be taking place behind the scenes. That's where checks and balances in the Software Development Life Cycle (SDLC) and a good Application Lifecycle Management (ALM) platform come into play, but for now, a basic understanding of what each requires is in order.

How often do you create a new ASP.NET Core with Angular project? Seldom, correct? If that`s the case, you may have forgotten the little nuances with adding a new API controller and getting it to work with Angular while debugging. Seeing this 404 error and then testing the default WeatherForecast APIController and seeing that work may drive you crazy, as it just recently did to me while creating a POC. I have learned from my many years of experience that a bug that takes longer than 30 minutes to figure out is usually something very simple as was the case here.