Hi everybody, A couple weeks ago Agustin ported the Prism’s PopupChildWindowAction for Silverlight to WPF: Prism: InteractionRequest and PopupModalWindowAction for WPF applications As you can read in its blog post, his PopupModalWindowAction had some limitations when defining a custom ChildWindow, mainly because you cannot reuse the same instance of a Window after it’s closed. Talking... read more
Hi everybody, Since the version 4.1 of Prism, the RegionActiveAwareBehavior has been modified to be able to sync the state (that is, the IsActive property of the IActiveAware interface) of “child” views and view models with their parents through the inclusion of the SyncActiveState attribute. However, a user in the following work item has posted... read more
Hi everybody, A couple of months ago I published a blog post (Regions inside DataTemplates in Prism v4) about a possible work around for placing a Prism Region inside a DataTemplate in WPF. However, a few days ago I was talking with Guido Maliandi (after he published his blog post about Binding to commands from... read more
Hi everybody, The AutoPopulateRegionBehavior provided in Prism (that is, the one that it’s used with the RegisterViewWithRegion method, as explained in this section of the Prism documentation) is a behavior that automatically populates a region with the views that have been registered for it as soon as it is created or when a new view registration occurs. This... read more
Note: You can find an updated another approach in this post. Hi everybody, There is a known issue in Prism where, if a Region is defined inside a DataTemplate, the Region is never register in the corresponding RegionManager. Based on our understanding, the region is created, but it does not get registered by the RegionManagerRegistrationBehavior... read more
Hi, this is my first Southworks post! I will be sharing my knowledge and experiences in this blog from now on. Until then try reading one of our other Southworks Blogs (http://blogs.southworks.net). See you soon!