Closed connellsharp closed 4 years ago
Yup, that's mentioned in the release notes
Still TODO
Now that Autofac 5.0 is out, there is still a lot to do. We'll be working on these things as fast as we can:
- Updating integration packages we support so they ensure compatibility with Autofac 5.
- Updating the documentation to reflect the above changes.
Some of this is sitting in branches ready to go, other things need to be done now that we have this core package out there.
If your favorite integration isn't ready yet, we're doing our best. Rather than filing "When will this be ready?" issues, consider pull requests with the required updates.
If I have to use Autofac 5.0.0, How can I solve this problem? I can't find a related discussion, thank you.
This is a different issue, but: you can't. Any time you see a major version upgrade (Autofac.Extras.DynamicProxy v5.0.0 to v6.0.0) it indicates a breaking change. In this case, the breaking change is the forced upgrade to Autofac core. It's always wise to read the release notes before taking any update. In this case, the release notes tell you about the forced upgrade. If you can't upgrade core Autofac, you can't take this upgrade either.
Now that Aufofac 5.0 has been released, the integration with Autofac.Extras.DynamicProxy throws an exception.
Here is a test repo demonstrating the error.
It looks to be because of this commit and that
ComponentRegistration.RaiseActivating
is now being called twice. This causes an error when calling the secondProxyGenerator.CreateInterfaceProxyWithTarget
: