Ошибка the type initializer for module threw an exception

Answers

• Sounds like your release build isn’t copying all the files it needs to run.  Verify that all the binaries that are needed are in the appropriate directory.  The output directory for debug is different than for release.

  Hope this helps,
  Michael Taylor — 11/23/05

I had one source code having 25 projects in single solution. It is consisting of both c++ as well as C# project. But now i wanted to call one of C# project(which is of windows application type) calls from a separate test project. I created a separate c# project and added the source reference, and created a object of source code class. it is building fine. but at the time of execution, it is throwing:

The type initializer for '<Module>' threw an exception

Please give me suggestion to resolve this issue.

Experienced a similar problem when catching the error with a try-catch… Upon removing the try-catch block the full trace indicated FIPS as the culprit. Toggling the registry switch to 0 for FIPS solved the problem in this case.

I have a c++/cli project and it’s a windows application. In debug mode we didn’t have any problems but after taking it to release mode this error start up. I searched and found some forum-answers but couldn’t help me solve this problem.
Please help me ….

Error :

An unhandled exception of type ‘System.TypeInitializationException’ occurred in Unknown Module.

Additional information: The type initializer for ‘Module’ threw an exception.

Updated 16-Nov-21 13:06pm

I had the same error and found that the class I was referencing was not the problem, but it had a static variable of another type declared that required another assembly to load. That assembly was built for a target platform of x86 (see Properties—>Build tab) however the main project was compiled for Any CPU. I rebuilt the older assembly for Any CPU… problem solved.

Here are some helpful steps for finding the root cause of this problem…

Click Debug—> Exceptions and check ON all the Thrown checkboxes. This will cause the debugger to stop on all first chance exceptions and will help you find the error under the Type Initializer error that you’re seeing. If it is related to another assembly, as mine was, you can use Microsoft’s Assembly Binding Log Viewer tool to help determine the problem.

Does the machine where the application is running has all the required dlls??

Maybe you are missing some interops in the local directory

I recently had the same problem, and it was because I was using Date.Parse on a missing element in the config file:

Date.Parse(System.Configuration.ConfigurationManager.AppSettings.Get(«frex»))

change your .net framework to lower

In my case (so many different cases where this shows up) I was initializing some static fields in their declaration, like this:

public class MyHelperClass
{
    readonly static SolidColorBrush BlueBrush = new SolidColorBrush(Colors.Blue);
    
    public static void ApplyBrush()
    { 
      
    }
}

When I moved the initialization into a static constructor, the exception was no longer thrown:

public class MyHelperClass
{
  readonly static SolidColorBrush BlueBrush;
  
  static MyHelperClass
  {
    BlueBrush = new SolidColorBrush(Colors.Blue);
  }
}

look the repository container in unity.config
<pre><pre lang="xml">
<unity xmlns="http://schemas.microsoft.com/practices/2010/unity">
  <alias type="App.Core.Interfaces.IRepositoryConfiguration, App.Core" alias="IRepositoryConfiguration" />
  <alias type="App.Repository.Mappings.SqlServer.SqlRepositoryConfigurer, App.Repository.Mappings.SqlServer" alias="SqlRepositoryConfigurer" />

  <container name="RepositoryContainer">
    <register type="IRepositoryConfiguration" mapTo="SqlRepositoryConfigurer" >
      <lifetime type="singleton"/>
    </register>
  </container>
</unity>
</pre></pre>

I was making an assignment in a constructor that didn’t have an error handling.

fileInfo = My.Computer.FileSystem.GetFileInfo(logDirLoc & logFileName)
writer = fileInfo.AppendText()

When I removed it the issue was solved.

tip: I looked through the error details and saw that a file couldn’t be found. That was it.

I faced the Same error that is «System.TypeInitializationException». This error is raised due to Static constructor .

Actually in my case i am accessing some value from the App.config and assigning that value in a static variable . The error is because of the App.config file . That means the app.config file is not well formed (I just missed some tag on app.config ). After putting the missing tag it works fine.

The type initializer for ‘Module’ threw an exception.
Just Run IISRESET

I had this problem also, but my solution wasn’t any of these. It was because I had an unmanaged class with a virtual function that returned a managed pointer.

class A
{
    virtual ManagedType^ Foo();
};

Apparently the C++/CLI runtime can’t handle this. Removing the virtual fixed the problem (luckily for me the virtual wasn’t needed in my case).

Ответы

• • Помечено в качестве ответа

    8 марта 2011 г. 9:37