Submitting a pull request to ensure the RezolveContainerAdapter is compatible with Rezolver 1.2, which I've just pushed to Nuget.
This release changes a few APIs and adds a significant performance improvement for the Asp.Net Core MS DI Extensions.
I've also taken the liberty of rewriting much of the registration code to use the .Register* extension methods for ITargetContainer.
The performance in the Child Container bench is still quite poor because of the dynamic compilation that's performed by the container - every time it runs it's recompiling the delegates for each type registered in the child container from scratch as it's a new container. This is something I'm planning on addressing in a future release.
Hi Daniel,
Submitting a pull request to ensure the RezolveContainerAdapter is compatible with Rezolver 1.2, which I've just pushed to Nuget.
This release changes a few APIs and adds a significant performance improvement for the Asp.Net Core MS DI Extensions.
I've also taken the liberty of rewriting much of the registration code to use the
.Register*extension methods forITargetContainer.The performance in the Child Container bench is still quite poor because of the dynamic compilation that's performed by the container - every time it runs it's recompiling the delegates for each type registered in the child container from scratch as it's a new container. This is something I'm planning on addressing in a future release.
Thanks for all your hard work!
Andras