Is the order of static class initialization in C# deterministic?

by

Straight from ECMA-334:

17.4.5.1: “If a static constructor (§17.11) exists in the class, execution of the static field initializers occurs immediately prior to executing that static constructor. Otherwise, the static field initializers are executed at an implementation-dependent time prior to the first use of a static field of that class.”

And:

17.11: The execution of a static constructor is triggered by the first
of the following events to occur within an application domain:

  • An instance of the class is created.
  • Any of the static members of the class are referenced.

If a class contains the Main method (§10.1) in which execution begins, the static constructor for that class
executes before the Main method is called. If a class contains any static fields with initializers, those
initializers are executed in textual order immediately prior to executing the static constructor (§17.4.5).

So the order is:

  • A.X used, so static A() called.
  • A.X needs to be initialized, but it uses B.X, so static B() called.
  • B.X needs to be initialized, and it is initialized to 7. B.X = 7
  • All static fields of B are initialized, so static B() is called. X is printed (“7”), then it is set to A.X. A has already started being initialized, so we get the value of A.X, which is the default value (“when a class is initialized, all static fields in that class are first initialized to their default value”); B.X = 0, and is printed (“0”).
  • Done initializing B, and the value of A.X is set to B.X+1. A.X = 1.
  • All static fields of A are initialized, so static A() is called. A.X is printed (“1”).
  • Back in Main, the values of A.X and B.X are printed (“1”, “0”).

It actually comments upon this in the standard:

17.4.5: It is possible for static fields with variable initializers to be observed in their default value state. However, this is strongly discouraged as a matter of style.

More Related Contents:

  1. When to use static classes in C# [duplicate]
  2. Can I add extension methods to an existing static class?
  3. Lifetime of ASP.NET Static Variable
  4. Why can’t I inherit static classes?
  5. Static vs non-static class members
  6. What is the use of static variable in C#? When to use it? Why can’t I declare the static variable inside method?
  7. When do static variables get initialized in C#?
  8. Are static class instances unique to a request or a server in ASP.NET?
  9. What does `static` mean in c#?
  10. Are static methods thread safe
  11. Static Indexers?
  12. Should C# methods that *can* be static be static? [closed]
  13. What’s the correct alternative to static method inheritance?
  14. Use dependency injection in static class
  15. How to access page controls inside a static web method? [duplicate]
  16. How can I get the value of a session variable inside a static method?
  17. Dependency injection with a static logger, static helper class
  18. Calling a Variable from another Class
  19. C# static member “inheritance” – why does this exist at all?
  20. C# – static types cannot be used as type arguments
  21. How to implement virtual static properties?
  22. Why choose a static class over a singleton implementation?
  23. Why must C# operator overloads be static?
  24. Are static members of a generic class tied to the specific instance?
  25. Order of static constructors/initializers in C#
  26. How do static properties work in an asp.net environment?
  27. Why is it impossible to declare extension methods in a generic static class?
  28. Why static fields initialization occurs before the static constructor?
  29. How does HttpContext.Current work in a multi-threaded environment?
  30. Is it possible to access an instance variable via a static method?

Leave a Comment