The Infragistics support team recently reached out to me asking for help with a customer’s WPF application experiencing a Prism region not found exception. After a little bit of digging, it didn’t take long to discover why app was throwing a Prism region not found exception.

The Prism region not found exception is usually cause when you are trying to define a region using the RegionManager.RegionName attached property to a control that is not part of the visual tree. Controls such as context menus, or flyout menus, are the main culprits for throwing the Prism region not found exception.

Want to know how to fix the Prism region not found exception? Watch this video.

Brian Lagunas

View all posts

Add comment

Your email address will not be published. Required fields are marked *

Follow Me

Follow me on Twitter, subscribe to my YouTube channel, and watch me stream live on Twitch.