prism-4

Disclaimer: Prism Novice. I'm reading up furiously to make up for lost time though :) Context: I need to write automated acceptance tests for a WPF application built using Prism. Issues: I find that it is convoluted trying to compose the backing ViewModels and everything that they need without the UI. I may be wrong here... Prism allows you to mark up the shell with named placeholders (regions). Different modules (isolated units) register their Views with the corresponding RegionNames. The Views also have a dependency on the ViewModel (ctor injection) which is injected via MEF/Unity. Showing

I'm developing a .NET 4.0 application using PRISM and MVVM, as well as WPF. I currently have a shell subdivided in regions, with views inserted in them. When the user clicks on a button in one of the views, I would like a custom-made modal dialog to be displayed on top of all the views, but still within the same shell. I looked at the StockTrader RI example and their implementation of the RegionPopupBehavior. Basically, they created a dependency property which allows them to define regions with a specific, custom-made behavior. The behavior is the one in charge of handling it's associated view

I am Unit Testing MVVM based application that uses prism and using mocking to test view model . I am able to call the constructor of my viewmodel class by passing mock objects of region manager and resource manager but when control goes inside constructor it fails at the following statement : private EventAggregator() { this.eventAggregatorInstance = ServiceLocator.Current.GetInstance<IEventAggregator>(); } It gives error : An unhandled exception of type 'Microsoft.Practices.ServiceLocation.ActivationException' occurred in Microsoft.Practices.ServiceLocation.dll Additional information:

Having working on WPF MVVM (prism) application, I would like to implement authentication as it is for ASP.NET form based authentication. I would like to restrict users going to screens where authorization is required. how can this be implemented in WPF application, as I am using PRISM. Assuming you are using Regions to navigate within your application, then your viewModels can implement the IConfirmNavigationRequest interface. There, you can use ConfirmNavigationRequest which takes a callback, to determine if the user has access to the view, and if not, deny it. Samples can be found here Check

I'm using WPF4 and PRISM4 for my new project. There is a single module with several views in it. The DI is done with unity. When I navigate from ViewA to ViewB for the first time, the ViewB is created and its constructor is called. But when I try to navigate to ViewB for the second, third time, the ViewB is not created, but existing instance is reused. I'm using IRegionManager.RequestNavigate for my navigation purposes. I've tried to pass TransientLifeTimeManager to RegisterType Unity methods, but to no avail. Is there a way to configure prism and/or unity to create a new view every time I

I am building a demo app to learn the navigation features of Prism 4. The app has two modules--each one has three Views: A UserControl with a text block ("Welcome to Module A") A RibbonTab (using a Region Adapter), and An Outlook-style Task Button (like Outlook's Mail, Calendar, and so on) The Shell has three named regions: "RibbonRegion", "TaskButtonRegion", and "WorkspaceRegion". The Views load into these regions. To test the basic setup, I registered all three Views with the Prism Region Manager, so that they would load at startup, and all worked as expected. Next, I modified the setup so

We are building a WPF Prism application. We have different developers working on different module projects, and multiple modules are injected into the main Application Shell. The main application is also a separate project. We also want to be able to use the modules in different applications. We do not want to have to name the Regions with the same names in every application. For instance, say we have a module to be used in two different applications. In one application, its developer may name the module's region "DetailsRegion," and in the other, its developer may name it "ResultsRegion."