All: All:

We have an WPF application using MVVM, PRISM and the XamTileManager 13.2. Views are injected dynamically into the xamTileManager using prism. Basically, each tile represents one view. The structure is as follows:

SessionTemplateView (WPF Tab Control)

• PTMTileTemplateView: View injected into Session Template Region

• MasterRegion (WPF ItemsControl)

  • TileManagerTemplateView - View injected into Master region

    • TileManagerRegion with xamTileManager

      • PTMPayTemplateView - View Injected into TileManager Region

        • PaymentsRegion(WPF ItemsControl)

          • PaymentsView injected into PaymentRegion

          • PaymentAmountsView injected into PaymentsRegion

          •  

      • PTMPenTemplateView -  View Injected into TileManager Region

        • PenaltiesRegion(WPF ItemsControl)

          • PenaltiesView injected into PenaltiesRegion

          • PenaltyAmountsView injected into PenaltiesRegion

• RLRegion (WPF Items Control)

• Lookup View - View injected into RLRegion

Every view has a corresponding view model. We have a concept of a session. Each session contains the TileManagerTemplateView. When we close the session we remove the region and publish shutdown events to all the views. All the views and view models have Finalize events that dispose the VM and view. The View and VM in the RL Region, which are not injected into the TileManagerRegion, do get unloaded from memory when the session is closed. Also, the Views from the Master Region get unloaded as well. The issue seems to be the VMs in the Master Region which contains the TileManager. Not only do they not get unloaded, a new instance of the view model gets created every time the tile gets expanded. The VMs do not have any data in the collections, lists etc., but they do remain in memory. We are not sure how to remove these View Models or how to prevent them from being created in the first place.

Any help or recommendations will be highly appreciated.

Regards,

Adolfo