It always seemed like something that could be handled by a unit test. Assuming your registration code is able to be called independently, validating it once with a test at build time seems much more useful than wasting time at every startup for something that will be more or less static.
this post was submitted on 09 Aug 2023
14 points (100.0% liked)
.NET
1484 readers
7 users here now
Getting started
Useful resources
IDEs and code editors
- Visual Studio (Windows/Mac)
- Rider (Windows/Mac/Linux)
- Visual Studio Code (Windows/Mac/Linux)
Tools
Rules
- Rule 1: Follow Lemmy rules
- Rule 2: Be excellent to each other, no hostility towards users for any reason
- Rule 3: No spam of tools/companies/advertisements
Related communities
Wikipedia pages
- .NET (open source & cross platform)
- .NET Framework (proprietary & Windows-only)
founded 1 year ago
MODERATORS
yeah, our unit tests def won't pass if we have a dependency loop so it's a waste of time checking every build.
it was crazy how difficult it was to find info on the setting and the right place to set it, considering the impact it was having.
Does this apply to ASP.NET Web Forms? :) Legacy dev is where the money's at, just be prepared to stare at build output for 95% of your life.