Modularity API Alignment

[dansiegel]

Description of Change

Moving what should be the final changes for the Modularity Alignment. This PR moves IModuleCatalog to the Prism.Core and further updates the API to rely on a more generic IModuleInfo than a concrete ModuleInfo type.

fixes #1290

Bugs Fixed

None.

API Changes

Reversed:

• The ModuleInfo.ModuleType property in Prism.Forms has been changed back to System.Type hiding the underlying string IModuleInfo.ModuleType. This will make updating easier on developers who may have explicitly defined the ModuleInfo from Prism 6.X.

Added:

• IModuleInfoGroup was added to Prism.Core to abstract the Groups, with concrete definitions required on the implementing Platform. NOTE This is not supported in Prism.Forms
• ModuleCatalogBase. This provides a base implementation for the ModuleCatalog in the Prism.Core.
  • Prism.Wpf and Prism.Forms ModuleCatalog both expose the Items property as a content property for XAML definitions
  • Prism.Wpf maintains the CreateFromXaml in it's implementation of ModuleCatalog.

Changed:

• IModuleCatalog -> has moved from Prism.Wpf to Prism.Core. Prism.Forms will now use the same IModuleCatalog as Prism.Wpf.
• IModuleTypeLoader -> changed signatures to use IModuleInfo
• ModuleManager in Prism.Forms introduces RaiseLoadModuleCompleted

Behavioral Changes

Prism.Forms ModuleManager will now resolve ModuleDependencies from the ModuleCatalog with the ModuleDependencySolver the same as Prism.Wpf

PR Checklist

• Has tests (if omitted, state reason in description)
• Rebased on top of master at time of PR
• Changes adhere to coding standard

[brianlagunas]

this looks good to merge

[lock]

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.