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
The number of packages to install and manage can become quite insane. Not to mention it's just silly having to specify the container for PrismApplication or ShinyStartup.
Proposal
Instead of installing:
Prism.DryIoc.Forms.Extended
Prism.DryIoc.Extensions
Prism.Forms.Extended
Prism.Container.Extensions
We would instead want to install the following anywhere we need the extended bits
Prism.Forms.Extended
Prism.Container.Extensions
Leaving just
Prism.DryIoc.Extensions | Prism.Unity.Extensions
Which could then only be added to the Platform projects if you wanted.
Benefits
PrismApplication could live inside Prism.Forms.Extended
Both PrismApplication and the PrismStartup for Shiny Support could use a common locator to pull in the container at runtime.
It makes it easier to swap out containers
Better Extensibility
The text was updated successfully, but these errors were encountered:
Description
The number of packages to install and manage can become quite insane. Not to mention it's just silly having to specify the container for PrismApplication or ShinyStartup.
Proposal
Instead of installing:
We would instead want to install the following anywhere we need the extended bits
Leaving just
Which could then only be added to the Platform projects if you wanted.
Benefits
The text was updated successfully, but these errors were encountered: