Lukas Grützmacher

For me (using IONOS Windows Hosting) switch to version 2.0.0 also "solved" the problem. Hope you will find the differences so that we can switch back to the latest version....

> I bluntly admit it's not at all visible, but you should also test cases to `Fake_should_method_throws` and `ClassesWithGuardEquals`. First I implemented the overload for `AndConstraint` in relation to the...

> ## Pull Request Test Coverage Report for [Build 2724304141](https://coveralls.io/builds/51104791) > * **1** of **1** **(100.0%)** changed or added relevant line in **1** file are covered. > * No unchanged...

> You can run `./build.ps1` locally and see the report in `TestResults/report/` (or something like that). I checked the report: Both classes are mentioned to be tested. So the new...

I'm wondering why there is no "comment" from coveralls with the coverage report!?

I found another bug...

Would be great to merge this PR without squashing because of the refactorings.

> If you would squash some of the commits that belong together and keep the refactoring and renames separate, we can. Hope, this is sufficient.

The method `Monitor` could get (optional) options to ignore specific events to be subscribed.

I recommend to ignore specific events instead of "exception when accessing any event". This looks very specific to your scenario. The options should be similar to exclusion in `BeEquivalentTo`.