Prism-Samples-Wpf | Samples that demonstrate how to use various Prism features | Form library

how to call it from other modules?

When a service (like the DialogService) is registered with the container, it will be injected into all constructors that request it as dependency if those are resolved from the container.

This works for public MyViewModel( IDialogService dialogService ) { ... } no matter where the code of MyViewModel resides, as long as it's called by the container. No matter where it resides, the view model has to be linked to its view (by naming convention or explicit call) to be found by the view model locator (and thus created "magically" by the framework) or you have to resolve it yourself (e.g. by injecting a Func< MyViewModel> or a hand-coded factory or - do not do this - by injecting the container or - avoid this, too - by calling new and providing the dependencies yourself).

All this works in exactly the same way for view models defined in the main app and those defined in modules.

If you want view injection or use the navigation framework and need to set an initial view, you can inject it or navigate to it using the region manager in the Prism application by overriding OnInitialized in App.xaml.cs. It is important that you call base.OnInitialized(); first, because it will call Show() on the shell window. Consequently, after this call the shell view is initialized and the region manager knows about its regions.

Binding is not relative to the TargetType of the style. Binding path is resolved against current DataContext of FrameworkElement after Style is applied (unless something changes Source, like explicit setting Source, or RelativeSource, or ElementName).

what happens here it that Prism RegionManager uses ViewA/ViewB as DataContexts for TabItems. Confirm it with the following code: