mvvm-light

I am fairly new to following the MVVM pattern. I am using MVVMLight. I am wondering how have multiple unique instances of the ViewModel with MVVM Light. For exmaple I have an application that can open n number of windows. Each uses the same Viewmodel. I am curious in MVVM whats the best practive to give them there own instance. If I follow the MVVM Light example the ViewModeLocator will have only a static instance which each window will end up using. Thanks in advance. You are not obliged to use ONLY the static view models in the view model locator. That approach only makes sense if your views

My ViewModel instantiate resource that must be released when the program exits. this in all my ViewModels: public class MainViewModel : ViewModelBase { LocalServer Server { get; set; } Resource MyResorce { get; set; } public MainViewModel(LocalServer server) { this.Server = server; MyResource = new Resource(); } public override void Cleanup() { if (MyResource != null) MyResource.Close(); MyResource = null; base.Cleanup(); } } this in ViewModelLocator public class ViewModelLocator { public ViewModelLocator() { ServiceLocator.SetLocatorProvider(() => SimpleIoc.Default); SimpleIoc.Default

I am using MVVM Light and have used the packaged messenger system to communicate between view models, however I have hit a bit of a dilemma! Basically when a user clicks on a customer record the corresponding view is opened and with it the CustomerViewModel is instantiated. At this point the CustomerViewModel requires the selected customers ID from the previous view model ( ViewAllCustomersViewModel ) so that it can get selected customers info which the view binds to (still following?). So initially my thought was too send that ID in a message from the ViewAllCustomersViewModel (where the

I am using MVVM-Light RelayCommand private ICommand myRevertCmd; public ICommand Revert { get { if (myRevertCmd == null) { myRevertCmd = new RelayCommand(RevertExecute, CanRevertExecute); } return myRevertCmd; } } private void RevertExecute() { searchType = SearchType.Revert; SearchStart(); } private bool CanRevertExecute() { return isRevertEnabled; } I have some code that changes the value of isRevertEnabled but the linked button does not change. After some searching I found that you can use to force the re-evaluation of the button states // force the GUI to re-evaluate the state of the

I'm trying to figure out the best way to bubble up PropertyChanged events from nested Properties in my ModelView. Say I have my ModelView PersonModelView which has a Property PersonModelView.Address . Address in turn has a property City . When I bind to City in my view, I would do something like {Binding Address.City} . My problem is that even if Address implements INotifyPropertyChanged , the binding will not get updated because it is handling PropertyChanged on the PersonModelView , not Address . I think I have two options: (1) change the source of the binding (or change the DataContext ) to

Building a WP7 app using MVVM light for my view models. I'm using the ViewModelLocator that gets added when you add the library through NuGet. Works great but now I need to get access to a ViewModel from code. In my code the user clicks a button and I need to search the MainViewModel (which contains several view models) and find one based on the criteria the user entered. Normally I would just response to the Click event of the button but I don't have an instance variable of the ViewModelLocator class to get a hold of the MainViewModel to perform the search. With the default template (non

I have decided to use the MVVM Light library to help design a UI. After tons of research and trial and error, I have yet to find the answers I am looking for. I've googled and read each StackOverflow question I can find, however, my problem seems to be unique on SO. I wish to design a UI with a single window and populate it with different Views/UserControls. I do NOT want a shared navigation bar among the UserControls nor do I want multiple windows to pop-up. Each View/UserControl should bind to its own ViewModel, while the MainWindow will bind to a MainViewModel. Example scenario - MainWindow

I have the following scenario: I have one window say MainWindow where I am displaying the list of activities as per the specific user from the database. There is a one button present on the window. By clicking on that button a new window is getting opened having all the list of activities from the master table. Now I want add a chechbox on the second window against each item dynamically so that user can select/deselect the activities. Those selected/deselected values should save in the database and Parent/MainWindow should refreshed after clicking on the done button and changes should reflect