MOQ 4.0: The type initializer for 'Moq.Mock`1' threw an exception

Question

I'm getting the exception

The type initializer for 'Moq.Mock`1' threw an exception.

using Moq 4.0 I've checked around on a couple of forums and they allude to using the Moq-NoCastle version. I've tried both this and version in the Moq folder. Both with the same result.

I've got a solution with 2 projects, one for my interface, one for my tests. My main project has 2 files:

IMyInterface.cs:

using System;

namespace Prototype
{
    public interface IMyInterface
    {
        int Value { get; set; }
        void ProcessValue();
        int GetValue();
    }
}

My program.cs file has just the default code that's generated with the project.

My test project has a single file for my dummy test - TestProgram.cs

using System;
using NUnit.Framework;
using Moq;

namespace Prototype.UnitTests
{
    [TestFixture]
    public class TestProgram
    {
        Mock<IMyInterface> mock;

        [TestFixtureSetUp]
        void TestSetup()
        {
            mock = new Mock<IMyInterface>();
            mock.Setup(x => x.GetValue()).Returns(2);
        }

        [Test]
        public void RunTest()
        {
            IMyInterface obj = mock.Object; /* This line fails */
            int val = obj.GetValue();
            Assert.True(val == 2);
        }
    }
}

According to the documentation all is good and proper, and it compiles nicely. The problem comes when I try to run the test. It gets to the line marked above and crashes with the exception:

The type initializer for 'Moq.Mock`1' threw an exception.

I can't see what's going wrong here, can anyone shed some light on it?

score 10 · Answer 1 · answered Jan 26 '17 at 12:07

10

This occurred to me when I updated the Castle.Core NuGet Package to the version 4.0.0. Something changed that is does not work properly with latest Moq (v4.5.30) at this moment.

I solved this by going back to the Castle.Core version 3.3.3.

answered Jan 26 '17 at 12:07

Alfa Morales

101
1
2

Yes Alfa, Agree with you. SetUp : System.TypeInitializationException : The type initializer for 'Moq.Mock`1' threw an exception. ----> System.TypeInitializationException : The type initializer for 'Moq.Proxy.CastleProxyFactory' threw an exception. ----> System.IO.FileLoadException : Could not load file or assembly 'Castle.Core, Version=4.0.0.0, Culture=neutral, – Rasika Dec 06 '18 at 21:44

score 4 · Accepted Answer · answered Oct 01 '10 at 23:53

4

I was able to run your test successfully after making the following changes:

Made TestSetup() public
In RunTest, changed int val = obj.Value to int val = obj.GetValue() - this was just to get the Assert to pass.

I'm not familiar with NUnit (I use xUnit), but my guess is TestSetup() being private was the problem. When that method is private, NUnit shows this exception for me:

Prototype.UnitTests.TestProgram.RunTest:
Invalid signature for SetUp or TearDown method: TestSetup

Maybe you are using an older version of NUnit that handled this situation differently (I just downloaded 2.5.7.10213).

HTH

answered Oct 01 '10 at 23:53

Jeff Ogata

56,645
19
114
127

Thanks. It looks like the 'public' accessor needed to be set on the setup. What I couldn't figure out was when I used the debugger to debug the test, it actually ran through that method. So my assumption was that it didn't need to be public. – BenAlabaster Oct 03 '10 at 16:27
You're welcome. Sounds like NUnit was behaving strangely, and not giving good feedback. – Jeff Ogata Oct 04 '10 at 16:52

score 3 · Answer 3 · answered Nov 22 '18 at 13:26

I had a similar exception with Moq (it had previously worked fine).

For me the solution was to use NuGet to uninstall Moq and the assembly that the exception mentioned. And then re-install Moq using NuGet and apply any NuGet updates that subsequently appeared.

score -1 · Answer 4 · answered Apr 30 '19 at 15:03

I also had this issue using Moq, but slightly different than Richard.

My error was the following.

Message: System.TypeInitializationException : The type initializer for 'Moq.Mock`1' threw an exception. ---- System.IO.FileNotFoundException : Could not load file or assembly 'Microsoft.AspNetCore.Razor.Runtime, Version=2.1.1.0, Culture=neutral, PublicKeyToken=adb9793829ddae60'.

In my case I didn't have to remove Mock, install the missing Assembly in the correct version. I don't know why this was only an issue now. The issue happend after merging branches, but both branches didn't have either assemblies nor showed this error before. However, end good all good.

MOQ 4.0: The type initializer for 'Moq.Mock`1' threw an exception

4 Answers4