public an interface of the list and investigation of how to use the Prism.WPF

Introduction

[WPF] Added support for IDestructible #1709 1709 made as IDestructible which is in seems to be added to the Prism.Wpf.

If there is anything to the interface that is published by a look at this in the first place Prism.Wpf, because the question interface that must be implemented with the use side is that what it is occurs, public interface interface on Prism.Wpf It was investigated.

Survey date is the end of 2019/3. I'm sorry if there omission.

Prism

Name
original comments
Comments

IActiveAware
Interface that defines if the object instance is active and notifies when the activity changes.

There was a page that explains. RegionActiveAwareBehavior seems is processing.

Prism.Logging

Name
original comments
Comments

ILoggerFacade
Defines A Simple Logger Facade To Be Used By The Prism Library.

There was a page that explains. EmptyLogger , DebugLogger , TextLogger and TraceLogger are available in the standard. ILoggerFacade You can use your favorite logger if implemented in yourself. Because there is a sample that was replaced in Log4Net leave pasted link. It will use by injecting when you use.

Prism.Events

The so-called observer pattern function is for (PubSub pattern?).

Name
original comments
Comments

IEventAggregator
Defines an interface to get instances of an event type.

There was a page that explains. This is used to inject not implement by themselves.

IDelegateReference
Represents a reference to a <see cref="Delegate"/>.

DelegateReference has been implemented in. This class is used internally by the Prism Library. It's right.

IEventSubscription
Defines a contract for an event subscription to be used by <see cref="EventBase"/>.

EventSubscription has been implemented in. This is unlikely need to be aware of is also the use side.

Prism.Interactivity.InteractionRequest

This function is for the dialog. IDialogService is ish alternative to.

InteractionRequest is I want be left.

Name
original comments
Comments

IInteractionRequestAware
Interface used by the <see cref="PopupWindowAction"/>. If the DataContext object of a view that is shown with this action implements this interface it will be populated with the <see cref="INotification"/> data of the interaction request as well as an <see cref="Action"/> to finish the request upon invocation.

There was a page that explains. The reference here and here and here as well.

Iconfirmation: Inotification

Represents an interaction request used for confirmations. [Obsolete("Please use the new IDialogService for an improved dialog experience.")]
Same as above

Inotification
Represents an interaction request used for notifications. [Obsolete("Please use the new IDialogService for an improved dialog experience.")]
Same as above

IInteractionRequest
Represents a request from user interaction. View models can expose interaction request objects through properties and raise them when user interaction is required so views associated with the view models can materialize the user interaction using an appropriate mechanism. [Obsolete("Please use the new IDialogService for an improved dialog experience.")]
Same as above

Prism.Ioc

This function is related to container.

Name
original comments
Comments

IContainerRegistry

There was a page that explains. PrismApplicationBase appeared at. Because it is specified in the formal argument where it is used. It is for registration. It is implanted in the ViewModel, such as not to come by.

IContainerProvider

IModule it appeared in. Here it is for the resolution. It is implanted in the ViewModel, such as not to come by.

IContainerExtension: IContainerProvider, IContainerRegistry

This is to come Once injected in the ViewModel and the like. You will need If you think trying to register a complex solution and the resulting instance in there.

IContainerExtension<TContainer>: IContainerExtension

I did not know where you are using. Or call GetContainer by injecting IContainerExtension If you think trying to get a specific container (has been defined as Extension), if you use the DryIoc as if injected from the first as DryIoc.IContainer (specific container. Use by by'm container type location of the IContainer is different) I went into the hand.

IAutofacContainerExtension: IContainerExtension<IContainer>
Provides customization extensions for Autofac Applications
Prism.Autofac.Ioc was in the name space. Should that can be used if you are using the Autofac to the container.

Prism.Services.Dialogs

This function is for the dialog. In 2019/3 the end point has been added in Prism7.2pre.

Name
original comments
Comments

IDialogService

Here it is described in.

IDialogAware

Ditto

IDialogParameters
TODO: this can eventually be replaced with INavigationParameters
Same as above

IDialogResult

Ditto

IDialogWindow

Ditto

Prism.Navigation

It became the motivation of the investigation Idestructible has been placed.

It is located in the Prism.Core-ish place, but most have not likely to use the Prism.Wpf.

Name
original comments
Comments

INavigationAware: INavigatedAware, INavigatingAware

Provides a way for ViewModels involved in navigation to be notified of navigation activities.
The same name of the type were using there in Prism.Wpf be in Prism.Region.

Idestructible

(In the 2019/3/end we anticipate somehow behavior from the code because it does not yet entered in 7.2pre.) To implement the ViewModel. DestructibleRegionBehavior at the time of such a NotifyCollectionChangedAction.Remove Behavior is added that Idestructible seems to me call Destroy of. It feels destructor Toka like a finalizer of the screen.

INavigatingAware
Provides a way for ViewModels involved in navigation to be notified of navigation activities prior to the target Page being added to the navigation stack.
Has been placed in Prism.Core ish place has been used in Prism.Wpf is unlikely.

INavigatedAware
Provides a way for ViewModels involved in navigation to be notified of navigation activities after the target Page has been added to the navigation stack.
Same as above

INavigatedAwareAsync
Provides a way for ViewModels involved in navigation to be notified of navigation activities after the target Page has been added to the navigation stack.
Same as above

INavigationService
Provides page based navigation for ViewModels.
Same as above

INavigationResult

Ditto

INavigationParametersInternal

Ditto

INavigationParameters: IEnumerable<KeyValuePair<string, object>>

Ditto

IConfirmNavigation
Provides a way for ViewModels involved in navigation to determine if a navigation request should continue.
Same as above

IConfirmNavigationAsync
Provides a way for ViewModels involved in navigation to asynchronously determine if a navigation request should continue.
Same as above

Prism.Regions

Function on the Region had been defined. Simply's just a problem that seems to inherit some of the interface, if only to use.

Name
original comments
Comments

INavigationAware
Provides a way for objects involved in navigation to be notified of navigation activities.
To implement the ViewModel. It can be prepared in a method called at the time of screen transition.

IConfirmNavigationRequest: INavigationAware

Provides a way for objects involved in navigation to determine if a navigation request should continue.

INavigationAware addition to ConfirmNavigationRequest to have been added. It can reject the screen transition if return to specify the false to continuationCallback to get in the formal argument.

INavigateAsync
Provides methods to perform navigation. Convenience overloads for the methods in this interface can be found as extension methods on the <see cref="NavigationAsyncExtensions"/> class.
There is a RequestNavigate to use when the screen transition. It should not also be used to implement in this alone.

IRegionNavigationService: INavigateAsync

Provides navigation for regions.

Here it is described in.

IRegionNavigationJournal
Provides journaling of current, back, and forward navigation within regions.
Same as above

IJournalAware
Provides a way for objects involved in navigation to opt-out of being added to the IRegionNavigationJournal backstack.
Same as above

IRegionNavigationJournalEntry
An entry in an IRegionNavigationJournal representing the URI navigated to.

RegionNavigationJournalEntry have been implemented to. Container class of history. To store explicitly history IRegionNavigationJournal use when specified by the argument of RecordNavigation of.

IRegionManager
Defines an interface to manage a set of regions and to attach regions to objects (typically controls).
Region is injected into the case you want to operate on. RequestNavigate can also.

IRegionMemberLifetime
When implemented, allows an instance placed in a <see cref="IRegion"/> that uses a <see cref="RegionMemberLifetimeBehavior"/> to indicate it should be removed when it transitions from an activated to deactived state.
Implementation in ViewModel to. Us to discard the screen and keep the false at the time of screen transition. RegionMemberLifetimeAttribute can also be specified in the attribute. RegionMemberLifetimeBehavior are controlled by. Also specify the ViewModel to View is not a true is returned.

Iregion: INavigateAsync, INotifyPropertyChanged
Defines a model that can be used to compose views.
may be implemented by inheriting If you want to make your own Region.

IRegionBehavior
Interface for allowing extensible behavior on regions. There was a page that explains.

IRegionBehaviorCollection: IEnumerable<KeyValuePair<string, IRegionBehavior>>
Defines the interface for a collection of <see cref="IRegionBehavior"/> classes on a Region.

IRegionBehaviorFactory: IEnumerable<string>
Interface for RegionBehaviorFactories. This factory allows the registration of the default set of RegionBehaviors, that will be added to the <see cref="IRegionBehaviorCollection"/>s of all <see cref="IRegion"/>s, unless overridden on a 'per-region' basis. [System.Diagnostics.CodeAnalysis.SuppressMessage("Microsoft.Naming", "CA1710:IdentifiersShouldHaveCorrectSuffix", Justification = "It is more of a factory than a collection")]

IRegionViewRegistry
Defines the interface for the registry of region's content.

IViewsCollection: IEnumerable<object>, INotifyCollectionChanged
Defines a view of a collection.

IRegionAdapter
Defines an interfaces to adapt an object and bind it to a new <see cref="IRegion"/>.

IRegionManagerAccessor
Provides an abstraction on top of the RegionManager static members.

DefaultRegionManagerAccessor there is no opportunity to internal so use but there is implemented in, should.

IRegionNavigationContentLoader
Identifies the view in a region that is the target of a navigation request.

IRegionCollection: IEnumerable<IRegion>, INotifyCollectionChanged
Defines a collection of uniquely identified by their Name.

IHostAwareRegionBehavior: IRegionBehavior

Defines a <see cref="IRegionBehavior"/> that not allows extensible behaviors on regions which also interact with the target element that the <see cref="IRegion"/> is attached to.
There was to Prism.Regions.Behaviors name space .

Prism.Modularity

Hen module function, et al. It is rather less investigation because it does not use so much.

Name
original comments
Comments

Imodule
Defines the contract for the modules deployed in the application.

There was a page that explains. Destructive change in Prism7.1 use has had a little changed.

IModuleCatalogItem
Marker interface that allows both <see cref="ModuleInfoGroup"/>s and <see cref="ModuleInfo"/>s to be [System.Diagnostics.CodeAnalysis.SuppressMessage("Microsoft.Design", "CA1040:AvoidEmptyInterfaces", Justification = "This is a marker interface")]

IAssemblyResolver
Interface for classes that are responsible for resolving and loading assembly files.

IModuleManager
Defines the interface for the service that will retrieve and initialize the application's modules.

IModuleTypeLoader
Defines the interface for moduleTypeLoaders

IModuleGroupsCatalog

IConfigurationStore
Defines a store for the module metadata.

IModuleInitializer
Declares a service which initializes the modules into the application.

IModuleInfo: IModuleCatalogItem

IModuleInfoGroup: IModuleCatalogItem, IList<IModuleInfo>, Ilist
IList must be supported in Silverlight 2 to be able to add items from XAML

IModuleCatalog
This is the expected catalog definition for the ModuleManager. The ModuleCatalog holds information about the modules that can be used by the application. Each module is described in a ModuleInfo class, that records the name, type and location of the module.

IModuleExport
Describe the Managed Extensibility Framework export of an IModule. This interface is used when importing classes exported with the ModuleExportAttribute. This interface and the ModuleExport class properties should match.
Prism.Mef.Modularity