moq4 | Repo for managing Moq | Mock library

Assigning new byte[] { 5, 6, 7, 8, 9 }; to the lambda parameter creates a new object, which is different than the original byte[64] that you created beforehand.

The only way your lambda can modify the values passed by reference is using that reference, not replacing it. i.e: buffer[0] = 5.

If SomeObject is your own code (and you should not mock what you don't own), consider a signature that returns the array instead, in line with CQS. You could then just use .Returns() in this case.

The construction issue you have is most likely that you're passing the mock object (e.g., db) rather than the mocked object (e.g., db.Object) to the mock constructors.

The verification in the example is using a specific instance (reference) of a ContactScore, which is not the instance (reference) used during the invocation.

Use It.Is<>() with a predicate to match the desired properties values of the argument.

The problem turned out to be some sloppiness in the VB.NET compiler which Moq didn't anticipate having to account for.

https://github.com/moq/moq4/issues/1067#issuecomment-706671833

It's been adjusted accordingly, which will be available in an upcoming release.

Many thanks to stakx for his excellent and speedy work on this.

The error is because ControllerContext.HttpContext property is not virtual, so Moq is unable to override it.

Consider using an actual ControllerContext and mocking a HttpContext to assign to the property