I have been using Ninject, and found that it’s a pleasure to work with. Everything is set up in code, the syntax is fairly straightforward and it has a good documentation (and plenty of answers on SO). So basically it goes like this: Create the view model, and take the IStorage interface as constructor parameter: … Read more
tl;dr Is it acceptable for a ViewModel to contain instances of domain models? Basically not because you are literally mixing two layers and tying them together. I must admit, I see it happen a lot and it depends a bit on the quick-win-level of your project, but we can state that it’s not conform the … Read more
By default, the TabControl shares a panel to render it’s content. To do what you want (and many other WPF developers), you need to extend TabControl like so: TabControlEx.cs [TemplatePart(Name = “PART_ItemsHolder”, Type = typeof(Panel))] public class TabControlEx : TabControl { private Panel ItemsHolderPanel = null; public TabControlEx() : base() { // This is necessary … Read more
You can simply add a custom dependency property to do this: public class CustomDataGrid : DataGrid { public CustomDataGrid () { this.SelectionChanged += CustomDataGrid_SelectionChanged; } void CustomDataGrid_SelectionChanged (object sender, SelectionChangedEventArgs e) { this.SelectedItemsList = this.SelectedItems; } #region SelectedItemsList public IList SelectedItemsList { get { return (IList)GetValue (SelectedItemsListProperty); } set { SetValue (SelectedItemsListProperty, value); } } … Read more
You say “creating window instance and showing window from view model is violation of MVVM”. This is correct. You are now trying to create an interface that takes a type of view specified by the VM. This is just as much of a violation. You may have abstracted away the creation logic behind an interface, … Read more
The delegate method used in this and the linked answer can be used in any parent-child relationship and in either direction. That includes from a child view model to a parent view model, a Window code behind to the code behind of a child Window, or even pure data relationships without any UI involved. You … Read more
Jesse Liberty of Microsoft has a great concrete walk through on how to make use of the messaging within MVVM Light. The premise is to create a class which will act as your message type, subscribe, then publish. public class GoToPageMessage { public string PageName { get; set; } } This will essentially send the … Read more
I strongly disagree with the concept that the Model should not implement the INotifyPropertyChanged. This interface is not UI specific! It simply informs of a change. Indeed, WPF heavily uses this to identify changes, but that doesn’t mean it is an UI interface. I would compare it to the following comment: “A tire is a … Read more
It really depends on what you are trying to achieve, and how much infrastructure you want in place already, plus the ease with which you can find samples that help you out. I’m going to declare an interest here, because I’ve been actively involved in at least one MVVM framework, and I’ve had input into … Read more
This isn’t MVVM. You should not be creating UI elements in your view model. You should be binding the ItemsSource of the Tab to your ObservableCollection, and that should hold models with information about the tabs that should be created. Here are the VM and the model which represents a tab page: public sealed class … Read more