A while back, Roman Turovskyy wrote FakeItEasy: Be Careful When Wrapping an Existing Object, an interesting post highlighting some of the difficulties of faking classes (as opposed to interfaces, which by virtue of having no behaviour of their own, are quite a bit more predictable). It's well-written and I enjoyed …
As of version 1.18.0, a client-supplied bootstrapper can be used to determine which external assembly files are scanned during startup.
Last time, I talked about how [FakeItEasy extension scanning had improved in version 1.13.0][betterscan]. While this change has dramatically improved startup times in many situations …
A few weeks ago, I wrote about the problems that FakeItEasy's
assembly scanning was causing while it was looking for user-defined extensions. To recap,
FakeItEasy was scanning all assemblies in the AppDomain and the
working directory, looking for types that implemented
IArgumentValueFormatter, IDummyDefinition, or
IFakeConfigurator. This process was quite slow …