Capture Variables with Closures: C#: Initialize Static Fields: Listing 3

There are several different ways to initialize static fields. In most cases, the worst choice is a static constructor. Handling literals as constants provides the best performance. For values that must be calculated at runtime, just-in-time creation is often the best approach if you have the discipline to always use a property. Otherwise, using a method when calling a method to initialize the static field is usually the best approach.

public class InitializationTest
{
   public const string First ="Foo";
   public static readonly string Second = "Foo";
   public static readonly 
      ReadOnlyCollection Third = GetInitialValue();
   public static readonly ReadOnlyCollection Fourth;
   private static ReadOnlyCollection fifthBacking;

   public const int Sixth = 1;
   public static readonly int Seventh = 1;
   public static readonly int Eighth = 
      GetInitialNumericValue();
   public static readonly int Ninth;

   static InitializationTest()
   {
      Console.WriteLine("In Constructor");
      var list =  new List();
      // TODO: Fill List
      Fourth = new ReadOnlyCollection(list);
      Ninth = 1 + 1 - 1;// Simulate runtime calulation
   }

   private static ReadOnlyCollection GetInitialValue()
   {
      Console.WriteLine("In GetInitialValue");
      var list = new List() ;
      // TODO: Fill List
      return new ReadOnlyCollection(list);
   }

   private static int GetInitialNumericValue()
   {
      Console.WriteLine("In GetInitialNumericValue");
      return 1 + 1 - 1;
   }

   public static ReadOnlyCollection Fifth
   {
      get
      {
         Console.WriteLine("In Fifth");
         if (fifthBacking == null)
         {
            var list = new List();
            // TODO: Fill List
            fifthBacking = new 
               ReadOnlyCollection(list);
         }
         return fifthBacking;
      }
   }
}
comments powered by Disqus

Featured

  • Full Stack Hands-On Development with .NET

    In the fast-paced realm of modern software development, proficiency across a full stack of technologies is not just beneficial, it's essential. Microsoft has an entire stack of open source development components in its .NET platform (formerly known as .NET Core) that can be used to build an end-to-end set of applications.

  • .NET-Centric Uno Platform Debuts 'Single Project' for 9 Targets

    "We've reduced the complexity of project files and eliminated the need for explicit NuGet package references, separate project libraries, or 'shared' projects."

  • Creating Reactive Applications in .NET

    In modern applications, data is being retrieved in asynchronous, real-time streams, as traditional pull requests where the clients asks for data from the server are becoming a thing of the past.

  • AI for GitHub Collaboration? Maybe Not So Much

    No doubt GitHub Copilot has been a boon for developers, but AI might not be the best tool for collaboration, according to developers weighing in on a recent social media post from the GitHub team.

  • Visual Studio 2022 Getting VS Code 'Command Palette' Equivalent

    As any Visual Studio Code user knows, the editor's command palette is a powerful tool for getting things done quickly, without having to navigate through menus and dialogs. Now, we learn how an equivalent is coming for Microsoft's flagship Visual Studio IDE, invoked by the same familiar Ctrl+Shift+P keyboard shortcut.

Subscribe on YouTube