prism-6

问题 I want to migrate a project written with Prism 4 into Prism 6. In Prism 4 the CompositePresentationEvent<T> type is under Microsoft.Practices.Composite.Presentation.Events namespace. But when I pulled Prism 6 from nugget and removed old Prism 4 references, I could not see this event type anywhere in Prism 6 namespaces. Anyone can help me a bit? 回答1: The CompositePresentationEvent has been removed in Prism 6. If I recall correctly, if was deprecated in Prism 5, and removed completely in Prism

问题 I want to migrate a project written with Prism 4 into Prism 6. In Prism 4 the CompositePresentationEvent<T> type is under Microsoft.Practices.Composite.Presentation.Events namespace. But when I pulled Prism 6 from nugget and removed old Prism 4 references, I could not see this event type anywhere in Prism 6 namespaces. Anyone can help me a bit? 回答1: The CompositePresentationEvent has been removed in Prism 6. If I recall correctly, if was deprecated in Prism 5, and removed completely in Prism

问题 I am struggling to understand how the PRISM INavigationService maps to the standard Navigation.PushAsync provided by Xamarin Forms. I have an application that I have started using XF. It consists of a MasterDetailPage that is the home page and the "Detail" ContentPage contains a number of buttons that are used to then navigate to other functionality. Within the App.xaml.cs, I set the Application.MainPage to an instance of my home page wrapped within a NavigationPage " MainPage = new

问题 I’ve upgraded my project today to Prism 6.3.0 and Unity 5.3.1. Before that, I had Prism 5 and Unity 4. Now I’m running into problems with the Prism.Unity.UnityBootstrapper : it seems that the Container field is still a Microsoft.Practices.Unity.IUnityContainer instead of Unity.IUnityContainer . I had hoped that the upgrade would cleanly cut all references to Microsoft.Practices.Unity off of my project, but it seems that I’m still forced to use the “old” Prism library, at least in parts. Why

问题 I have a problem when using Xamarin.Forms in conjunction with Prism.Forms (Unity) on an Android 5.1.1 (Lollipop) device. Specifically, if I navigate to/from forms with "animation: true" those forms do not always work correctly afterward - specifically, the forms are not always updated in response to a PropertyChanged event. The forms work perfectly on Android 6.0 and 7.1 (the only other devices I have available for testing). If I change all of my calls to INavigationService.NavigateAsync so

问题 I want to unit test a module by throwing messages at it via Event Aggregation to make sure it responds appropriately, either by setting properties appropriately, or by publishing other messages as a result. I am using Prism 6. In my project, the infrastructure project has: public class ImportantMessage : PubSubEvent<string> { } ModuleA publishes a message like this: eventAggregator.GetEvent<ImportantMessage>().Publish(importantString); ModuleB receives the message like this: eventAggregator

问题 Is there a way whereby I can identify a ChildViewModel instance, which was created by prism's ViewModelLocator, upon opening it's corresponding window? I would like to trigger that the ChildViewModel should load it's data, based on parameters originating from the MasterViewModel. In code, in MasterViewModel has an ICommand in a which is responsible for requesting opening a new child window by publishing an event, and there is a corresponding subscriber. public ICommand OpenNewChildWindow() {

问题 I am trying to create an app using Prism in Xamarin Forms. Xamarin Forms Version: 2.3.3.175 Prism Version: 6.2.0 The hamburger menu works in Android but when I run it UWP it won't display the icon and also when I navigate through menu, the menu totally disappears and I wont have the method go back to other pages too. In other words, I need to close and restart the app. Here is what I tried so far. After creating the prism project I added a MasterDetailPage: <MasterDetailPage.Master>

问题 I have a user control where I have multiple Prism regions defined for injecting views. I decided to use the Prism view navigation for dealing with switching my "SelectedMenuContentRegion" based on user actions (as shown below) and I have run into a problem. I am sure the problem is with my usage, but I have not been able to figure out what I am doing wrong. I have the following user control which contains a custom WPF control. <Grid> <commonwpfcontrols:NavigationPane Background="

问题 I am trying to have view models resolved using DI with Prism 6 and Unity in my WPF app and this works. However I don't know how to tell the framework which view should be merged with which view model. If I use the convention, i.e. have ViewModels, and Views namespaces, and classes ViewA and ViewAViewModel everything works, however I would like to have more flexibility to name and organize my classes and this is why I want to somehow tell the framework explicitly which view goes with which