UnityContainer usage and best practices
Is it wrong to use UnityContainer in an app to access references to objects from different parts of the application (but the same assembly)?

The application (WPF) has several regions that need to access each other and I have used UnityContainer to do that. For example, the "main" region (which is a drawing area) has a presenter behind it, that manages all it's business logic, and I have registered this instance of presenter in the container, and in other parts of the application where i need to access it i to control that region, i access it via UnityContainer. 

Not sure if that's a good practice or a bad one.
UnityContainer usage and best practices
===

Is it wrong to use UnityContainer in an app to access references to objects from different parts of the application (but the same assembly)?

The application (WPF) has several regions that need to access each other and I have used UnityContainer to do that. For example, the "main" region (which is a drawing area) has a presenter behind it, that manages all it's business logic, and I have registered this instance of presenter in the container, and in other parts of the application where i need to access it i to control that region, i access it via UnityContainer. 

Not sure if that's a good practice or a bad one.