System.TypeInitializationException
The exception that is thrown as a wrapper around the exception thrown by the class initializer. This class cannot be inherited.
Minimum version: >= 1.1 >= Core 1.0
Statistics
25
How to handle it
try
{
}
catch (System.TypeInitializationException e)
{
}try
{
}
catch (System.TypeInitializationException e) when (e.Message.Contains("something"))
{
}try
{
}
catch (System.TypeInitializationException e) when (LogException(e))
{
}
private static bool LogException(Exception e)
{
logger.LogError(...);
return false;
}How to avoid it
We haven't written anything about avoiding this exception yet. Got a good tip on how to avoid throwing System.TypeInitializationException? Feel free to reach out through the support widget in the lower right corner with your suggestions.
Links
YouTube videos
Possible fixes from StackOverflow
In my case, I got the issue after upgrading to version 4.5.4 and tried @user2713341 answer. It didn't work but put me in the right direction.
My project had no bindings for this library, so I added the binding and it worked
<dependentAssembly>
<assemblyIdentity name="System.Threading.Tasks.Extensions" publicKeyToken="cc7b13ffcd2ddd51" culture="neutral" />
<bindingRedirect oldVersion="0.0.0.0-4.2.0.1" newVersion="4.2.0.1" />
</dependentAssembly>
and it worked.
Note that it should be assembly version 4.2.0.1 even though the package version is 4.5.4.
Update Nuget Package
https://www.nuget.org/packages/System.Threading.Tasks.Extensions/
will solve your problem
Another possible reason: the app.config has duplicate sections.
A possible reason: init a static dictionary with duplicated keys.
The response from @Keyjote was at the root of the solution for me, but rather than cherry-picking the assemblies, I was able to just reinstall. This seemed to automatically repair the app.config file.
Tools -> Nuget Packet Manager -> Packet Manager Console
Update-Package -reinstall -Project <your project name>
This way you don't need to mess with the syntax or have to figure out the PublicKeyToken values.
If you want to do it for the whole solution, you can omit the -Project <> parameter.
Source: Stack Overflow