Add static ctor to DispatcherImpl to force late initialization of static UiThread property #2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Win32Platform.Initialize method contains registration of Windows related components. It also includes registration of IDispatcherImpl that uses DispatcherImpl.UIThread as an instance.
DispatcherImpl.UIThread property retrieves IPlatformThreadingInterface by invoke of AvaloniaLocator.
The thing is that DispatcherImpl.UIThread doesn't have static constructor - it leads to the case when static property might be initialized before Win32Platform.Initialize method call. Such premature initialization raises the error because AvaloniaLocator returns null for IPlatformThreadingInterface.
Adding static constructor to DispatcherImpl forces JIT to generate the code that initializes static property at the moment of property invocation.