Question

OK, I am baffled at this point. Moq is not calling my one method, yet the assert on verify does show it is calling all my other methods that are not parameterless. I have even added the following:

.Throws<Exception>()

just to see if it would even throw, and still nothing (but adding it to other methods works). I know the object being used is my mock because I added a call that IS being logged immediately after the call that is not.

The method name is Finalize(). I doubt the naming of the method is the problem, but I have tried everything else.

Code After simplifying down to simplest solution by making the main method public:

  var asyncRecognizerMock = new Mock<AsyncRecognizer>();
  var asyncRecognizerFactoryMock = new Mock<AsyncRecognizerFactory>();
  var trainerMock = new Mock<Trainer>();
  trainerMock.Setup(trainer => trainer.Finalize()).Verifiable();
  var trainerDataRepository = new TrainerDataRepository(asyncRecognizerFactoryMock.Object, asyncRecognizerMock.Object);

  trainerDataRepository.FinalizeTrainer(trainerMock.Object);

  trainerMock.Verify(trainer => trainer.Finalize(), Times.Once());

My method is now:

public void FinalizeTrainer(Trainer wordTrainer)
{
  wordTrainer.Finalize();
}

Also, Moq is 4.0.10827.0 running against .Net 3.5

Answer 1

Rename your method to something other than Finalize. If I copy/paste your code and rename the method, it starts to work fine.

It also generates a compiler warning CS0465, and should be avoided.

The reason this doesn’t work is that Finalize is actually sort of a reserved name for the class destructor. If you write this C# code:

public class Trainer
{
    ~Trainer()
    {
        int x = 1;
    }
}

The compiler actually names the destructor Finalize() in the IL code:

.method family hidebysig virtual instance void 
        Finalize() cil managed
{
  // Code size       16 (0x10)
  .maxstack  1
  .locals init ([0] int32 x)
  .try
  {
    IL_0000:  nop
    IL_0001:  ldc.i4.1
    IL_0002:  stloc.0
    IL_0003:  nop
    IL_0004:  leave.s    IL_000e
  }  // end .try
  finally
  {
    IL_0006:  ldarg.0
    IL_0007:  call       instance void [mscorlib]System.Object::Finalize()
    IL_000c:  nop
    IL_000d:  endfinally
  }  // end handler
  IL_000e:  nop
  IL_000f:  ret
} // end of method Trainer::Finalize

In fact if you try to add both a destructor and a Finalize method:

public class Trainer
{
    ~Trainer()
    {
    }

    public virtual Finalize()
    {
    }
}

This code will no longer compile, because those 2 methods are the same thing. Tricky, eh? 🙂

It is also noted in ECMA-335:

I I.10.5.2 Instance finalizer

The behavior of finalizers is specified
in Partition I. The finalize method for a particular type is specified
by overriding the virtual method Finalize in System.Object.