Static Constructor Failures and Declaration Order

added by DotNetKicks
5/5/2020 3:00:22 PM

241 Views

I ran into an ugly problem today with an application where nested static constructors where not doing the expected thing - failing to provide a value when one should be available. It turns out the issue has to do with constructor calls nesting and the order in which auto-initialized values are assigned.


0 comments