Scott Moxham

I'm having exactly the same issue with the same pattern as @POnakS. It's frustrating that I'm having to add a lot of ! in my code after checking for null.

I'm also having this problem. However, I added Microsoft.EntityFrameworkCore.Design 6.0.1 instead of Tools from GitHub.

@CzBuCHi your alternative: `value?.Should()?.BeNull();` gets rid of the warnings, it will not do what you want. If `value` is `null`, then the assertion for null will never be executed because...