You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 2, 2019. It is now read-only.
specify mechanism to define which types to proxy and how to retrieve these
maybe more along the lines of Castle DynamicProxy: Request the proxied type and
Interface proxy: auto-create implementation
Class-proxy: auto-create wrapping class, same public members etc, but implementation is forwarded to actual "real" instance of "real" class.
What are the downsides over the current approach? Currently a class-proxy means modifying the class to inserting method-decorating code and ctor-arguments, which is less than ideal as it makes it impossible to instantiate the class without proxying/interceptors.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Allow proxying 3rd party assembly types.
What are the downsides over the current approach? Currently a class-proxy means modifying the class to inserting method-decorating code and ctor-arguments, which is less than ideal as it makes it impossible to instantiate the class without proxying/interceptors.
The text was updated successfully, but these errors were encountered: