First-chance exception thrown when registering open-generic type with type constraint about simpleinjector HOT 3 CLOSED

Patch release v5.4.2 has been published to NuGet.

Thank you for raising this issue.

from simpleinjector.

Thanks for responding to my issue so quickly. I hadn't noticed these exceptions being thrown in VS. I must have set something to suppress them. I'll update to the latest version of the package when I get a chance.

from simpleinjector.

When it comes to building generic types, sometimes the only way to verify that a type matches certain type constraints is to try build the type. I believe that there's now some sort of CanCreateGenericType method in .NET 6 or 7, but that's of to little use of Simple Injector, which needs to be compatible with older frameworks as well. The problem, unfortunately, is that CreateGenericType will throw an exception when the type constraints don't match. In that case Simple Injector catches the exception, but now knows that the type constraints didn't match.

This wasn't a big issue with older Visual Studio versions. More recent versions of VS, however, automatically break the debugger when a first-chance exception is encounters; even if it's not your own code. This new VS behavior is quite troublesome, as it stops the developer flow and can leave you in a confused state. I myself burned many hours tracking down a bug that didn't exist because I didn't realize that I was looking at a first-chance exception. Because of this change in behavior, quite some big internal changes were made in Simple Injector v5 to prevent most first-chance exceptions from occurring. I wrote more extensively about this change here.

Unfortunately, for the time being, Simple Injector can't prevent all first-chance exceptions from happening. On the plus side, these first-chance exceptions are harmless, you can ignore them, and you can configure your IDE to suppress them.

That said, using the code you provided, I've been looking at the code base and did notice that in your case (which I consider to be a happy-path scenario) the first-chance could actually be prevented. And even better, the type constraint check can be skipped, which improves performance of the registration process.

I will push a patch release shortly that fixes this issue.

from simpleinjector.