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.
Enable support for StaticProxy.Fody in scenarios where the user does not use a DI Container.
Ideas / Alternatives:
Add an alternative to new by something like StaticProxy.New(() => new MyProxiedType(argument1, argument2), .. list of interceptors...) which, upon compilation, will be replaced by `new MyProxiedType(argument1, argument2, interceptors)
same syntax but no IL-Weaving: use Activator.Activate to supply all parameters
Use a syntax as in Ninject's ".ToConstructor" binding to specify
other?
To progress, first investigate the constraints these alternatives have (for example, are there targets where Activator.Activate is not supported? Are Expressions supported?).
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.
Enable support for StaticProxy.Fody in scenarios where the user does not use a DI Container.
Ideas / Alternatives:
new
by something likeStaticProxy.New(() => new MyProxiedType(argument1, argument2), .. list of interceptors...)
which, upon compilation, will be replaced by `new MyProxiedType(argument1, argument2, interceptors)Activator.Activate
to supply all parametersUse a syntax as in Ninject's ".ToConstructor" binding to specify
To progress, first investigate the constraints these alternatives have (for example, are there targets where
Activator.Activate
is not supported? Are Expressions supported?).The text was updated successfully, but these errors were encountered: