kicsiede

This is due to a bug in Android-Image-Cropper that has been fixed in 2.8, so updating the binding library should fix the issue.

When dealing with scoped instance resolution and dependency overrides, an inconsistency arises when attempting to resolve a service for the second time with different overrides. In the following example, I...

[feature request] have more control over dependency overrides

2

It would be beneficial to have more precise control over passing dependency overrides, along with support for named bindings. Currently, our approach is as follows: `container.Resolve([ instance1, instance2... ])` In...

netstandard/core compliancy

3

hello, is there any chance making this lib net-standard/net-core compatible?