Thursday, April 27, 2017

I recently added support for ASP.NET Core to my Tact.NET IOC Container, and I thought that I would share some of the interesting requirements I discovered while doing so. I had originally expected the default ASP.NET Core container would follow the same rules as the official Microsoft Unity container, but that turned out not to be the case!

1) Register is first in win.

The Unity container was last in win, and it would completely disregard the original registration. With ASP.NET Core you need to preserve the original registration and then treat all subsequent registrations as addition registrations that will only be resolved when ResolveAll is invoked, similar to keyed registrations in Unity. Which brings us to our next difference...

Search This Blog

About Tom

Tom DuPont is a Software Engineer. He has been a tool at CodeSmith, made love at Match, and now makes war for Blizzard. He specializes in C#, ASP.NET, and even that crazy JavaScript stuff. His views and opinions are his own.

Listen to Tom

Tom is a host on the QQ Cast, where he helps answer geek culture's most superfluous questions.