Blair Conrad

Thanks for the update, @ChristoWolf. I hope your workaround/solution continues to work for you.

Thanks for making us aware, @maxcherednik.

Hi, @maxcherednik. The dependency is the lowest version that FakeItEasy will work with. Leaving it as it is allows users to keep using the older Castle.Core if they have a...

Okay, I very quickly ran our specs (the main test project) using Castle.Core 5.1.1 on .NET 5.0. 12 tests failed, but it looked like they failed for reasons that would...

> where does this generic parameter name coming from No idea. FakeItEasy does not create (or change) generic parameters called "TEvent", as far as I can tell. Nor does a...

> I thought dummies are the cheap fakes. Depends on what you mean by "cheap". If you're looking at performance, it may be more work to create a Dummy than...

Hi, @Bludator. Thanks for your interest in FakeItEasy. The question about the method name is giving us at FakeItEasy National some small pause, since default interface methods are kind of...

Okay. Confirmed that the default interface implementation was not required to get the output you posted. So the question I see is why we say we failed for `FIEQuestions.Test+IFoo.Method` and...

I'm back with very little information, but in this message ``` Assertion failed for the following call: FIEQuestions.Test+IFoo.Method(x: Something 2) Expected to find it once or more but didn't find...

Thanks for continuing on this, @maxcherednik. I wonder, though. The leading thought is that a problem is in or below the Castle.Core project, it may be a better use of...