Regions

Note: This section has been merged with the UI Composition section. This page is kept to preserve the history and changes in this section, but it should no longer be consulted for resources about regions.

The root object in a composite application is known as the shell. The shell acts as a master page for the application. The shell contains one or more regions. Regions are place holders for content that will be loaded at run time. Regions are attached to UI elements such as a ContentControl, ItemsControl, TabControl or a custom control and manage the UI element's content. Region content can be loaded automatically or on-demand, depending on the application requirements. Typically, a region's content is a view. A view encapsulates a portion of your UI that you would like to keep as decoupled as possible from other parts of the application. You can define a view as a user control, data template, or even a custom control. A region manages the display and layout of views. Regions can be accessed in a decoupled way by their name and support dynamically adding or removing views. A region is attached to a hosting control. Think of regions as containers into which views are dynamically loaded. Below you will find some resources that complement the information about this subject on the corresponding chapter in the Prism MSDN documentation.

Last edited May 4, 2011 at 4:46 PM by GuidoMaliandi, version 18

Comments

No comments yet.