Статическая инициализация гарантирует одноэлементную потокобезопасность? (C#) [дубликат]

that the constructor will fully complete before any other thread can get a reference to the object?

The static initializer will be invoked once only (by the system, at least) per AppDomain, and in a synchronized way, taking "beforefieldinit" into account. So assuming you don't do anything bizarre, any static fields assigned in the static initializer should be OK; any other attempts to use the static field should get held (blocked) behind the static constructor.

the reference to the new object is assigned only after the constructor completes

It happens when it happens. Any static field initializers happen before what you typically think of as the constructor, for example. But since other threads are blocked, this shouldn't be an issue.

However:

• if your static initializer itself passes a reference outside (by calling a method with the reference as an argument (including "arg0"), then all bets are off
• if you use reflection to invoke the static constructor (yes, you can do this), crazyness often follows

Да; гарантия заключается в заявлении, что он будет выполняться только один раз для каждого домена приложения.

Это может быть небезопасно, только если оно может выполняться более одного раза; как сказано, не может, так что все хорошо :)