I do not know your exact scenario, but there is no Unresolve method in Unity, because when you call to the Resolve method it does not keep a reference of the new instances.
If you use the Unity RegisterInstance method to register views, please take into account that this is not the most recommended approach. Therefore, if you are doing it to get them available from different locations, you could switch to use
ViewDiscovery, which allows you to discover views in a cross-module way, and does not keep alive an object reference.
In Prism there are different approaches to make a view either visible or non-visible. But, in this particular case, the correct option would be to remove the detail views from its region when users close them. This way, the garbage collector should be able
to collect the detail views. This might be achieved in your scenario by using the following code line:
On the other hand, there are two known issues related with memory leak(s),
the first one is when using DelegateCommand (it was solved in Prism 2.1 & later), since it keeps an instance of the bound control and the view that contains such control is not released. And the
second one is when removing a view that contains child-regions.
For more information about these topics, you could take a look at the following posts in the
If it does not help in your scenario, please consider sharing any other relevant information that might help to clarify this situation.
Please let me know if this helps.