-
-
Notifications
You must be signed in to change notification settings - Fork 835
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
how to aply Autofac.Extras.DynamicProxy to a async method??? #856
Comments
I think this is related with Castle.Core not Autofac and AFAIK there is no There is an issue in castleproject/Core#107 about that. Take a look, might be helpful. |
Yup, this is a Castle question. Autofac can attach an interceptor for you, but the actual interception and how to implement the interceptors themselves is a Castle.Core thing. The issue mentioned by @osoykan is a great start on that. |
+1 |
Hey guys, Is there any progress being made on this? |
As noted above this is a Castle question, not Autofac. |
Thanks, @tillig, |
I would recommend pinging there. There is, quite literally, nothing that can be done on this from the Autofac side. |
Actually you can workaround it inside interceptor, here is an amusing workaround |
This worked for me:
|
how to aply Autofac.Extras.DynamicProxy to a async method???
invocation.Proceed() is a void method that i can not await
is there anybody can help me with this problem?
thanks a lot
The text was updated successfully, but these errors were encountered: