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
Right now AutoDI, looks for an entry point in the assembly and wires up its setup call inside of that. However, this can be problematic if you are producing a library that you expect to be consumed by other. Ideally AutoDI should work without the consumer of the library needing to know about AutoDI.
I am thinking something like the following:
New setting for turning this behavior on and off. Defaults to off.
When enabled, do the registration in the module initializer rather than looking for an entry point. Turning this on should disable the entry point registration.
The text was updated successfully, but these errors were encountered:
Right now AutoDI, looks for an entry point in the assembly and wires up its setup call inside of that. However, this can be problematic if you are producing a library that you expect to be consumed by other. Ideally AutoDI should work without the consumer of the library needing to know about AutoDI.
I am thinking something like the following:
The text was updated successfully, but these errors were encountered: