Debug and Release

My brief story which lead me to look to an unlikely culprit of what was causing a bug in my .NET Core application. The background This is a 3-tier application (front-end, business logic and data access layers) built in .NET Core. The application itself is actually a .NET Framework application that I am converting to .NET Core. I am converting this application not only for future support, but for performance improvements . If you haven't been on the bandwagon, .NET Framework isn't moving past version 4.8. As mentioned in the Microsoft blog , .NET Core will continue to get new features at a faster rate, and will be the preferred framework to build new apps moving forward. The application is a simple in that it has a data provider service supported by dependency injection , which uses a SQL connection to call a stored procedure to return data back into a model, which gets loaded into a view that contains a grid (ie. <table> ) on the webpage. Data is loaded base...