Question

I am interested in knowing why static destructors are not allowed in C#. Note that I am not supposing that they exist in any other language.

I could have a class like this one.

 class A
 {
      static A()
      {
         // here I can load a resource that will be avaliable for all instances 
         // of this class.
      }
 }

When the application ends I may need to release the resource.

So, the semantic of a static destructor could be the following: called when the application ends, for classes that contain it and were initialized in the app.

Answer 1

Your semantic is one possible one, but I guess you have not checked all effects it would have on the language. In most (more or less) dynamic languages I know, destruction is a much more complicated topic that it looks like. Why not call the destructor when the class is not referenced anymore? Or if the assembly is unloaded? In what order should destructor be called? …?

If you just want to execute some code when the application ends, have a look at the .Net documentation. There are easier and more reliable ways to do so.