Windsor currently does not support that, and it’s by design. The reasoning is that you should explicitly register types you need so that you dont get misconfigured object. There is however a possibility that there will be added a hook to create non-registered type at some point in the near future, as this is needed … Read more
At last, I found the answer! When DLLs in Prism modules are referenced, the .NET assembly resolution mechanism looks for the referenced assemblies in the /bin folder of the hosting application (i.e., the one with the Shell and Bootstrapper) rather than in the module’s bin directory (assuming you have set up your modules as separate … Read more
INotifyPropertyChanged The ViewModel should implement the INotifyPropertyChanged interface and should raise it whenever the propertychanges public class MyViewModel : INotifyPropertyChanged { private string _firstName; public event PropertyChangedEventHandler PropertyChanged; public string FirstName { get { return _firstName; } set { if (_firstName == value) return; _firstName = value; PropertyChanged(this, new PropertyChangedEventArgs(“FirstName”)); } } } } Problem … Read more
Main thing is, when you raise the interaction, provide a callback that is triggered when the interaction is finished. This callback gets the notification back and your interaction should have stored all potentially interesting return values there. Here’s an example… Relevant parts of the ViewModel: public InteractionRequest<SelectQuantityNotification> SelectQuantityRequest { get; } // in some handler … Read more
Probably you need to set the region manager manually, in the popup view’s code behind (constructor), like this: RegionManager.SetRegionName( theNameOfTheContentControlInsideThePopup, WellKnownRegionNames.DataFeedRegion ); RegionManager.SetRegionManager( theNameOfTheContentControlInsideThePopup, theRegionManagerInstanceFromUnity ); You’ll have to assign a name to the content control hosting the region and somehow acquire the region manager (ServiceLocator.Current.GetInstance<IRegionManager>()).
As with many frameworks that do a common task for you, you get: Tested by many more eyeballs: than just yourself. This (hopefully) includes unit tests, which you may or may not be doing while building your own framework. More readable for other developers: nobody else has experience with your custom MVVM framework. But if … Read more
In the past I ‘ve written an application that supports “live” editing of data objects from multiple locations: many instances of the app can edit the same object at the same time, and when someone pushes changes to the server everyone else gets notified and (in the simplest scenario) sees those changes immediately. Here’s a … Read more
So, assume you have a ViewModel with the following properties: public ObservableCollection<string> AllItems { get; private set; } public ObservableCollection<string> SelectedItems { get; private set; } You would start by binding your AllItems collection to the ListBox: <ListBox x:Name=”MyListBox” ItemsSource=”{Binding AllItems}” SelectionMode=”Multiple” /> The problem is that the SelectedItems property on ListBox is not a … Read more