-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
XF Modularity Enhancements #1139
Comments
…ey are added after manger.Run() PrismLibrary#1139
Option 4 is not a scenario that needs to be handled. |
Autofac Modules in Prism Forms should also be updated to support a more traditional Module approach public interface IAutofacModule : IModule
{
void Initialize(ContainerBuilder builder);
}
public abstract class AutofacModuleBase : IAutofacModule
{
public void Initialize() => new NotImplementedException();
public abstract void Initialize(ContainerBuilder builder);
} This would allow Prism.Autofac.Forms to then provide it's own ModuleManager with the PrismApplication's ContainerBuilder so that it can pass the builder into the modules |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
The following enhancements should be added to make Prism Modularity easier to work with:
AddModule
InitializationMode.WhenAvailable
, and AFTERIModuleManager.Run()
has been called.The text was updated successfully, but these errors were encountered: