Resolving ViewModel's commands from Controller? (PRISM) - command

Question

How would I go about resolving a ViewModel's commands from a controller?
Right now I'm having to dependency inject the UnityContainer into the ViewModel via constructor, and resolve the ICommand with a string. I don't really want to have to pass the container to my viewmodel, and would prefer to keep it in my controller.
These are just snippets, not the whole thing. Not that they're that complex of classes yet though while I try to learn.
ViewModel
private ICommand loadedCommand;
public ICommand LoadedCommand
{
get { return loadedCommand; }
set
{
loadedCommand = value;
RaisePropertyChanged(() => this.LoadedCommand);
}
}
public MainViewModel(IUnityContainer container)
{
LoadedCommand = container.Resolve<ICommand>("LoadedCommand")
}
Controller
DelegateCommand LoadedCommand;
new DelegateCommand(() => ViewLoaded());
Controller
Container.RegisterInstance<ICommand>("LoadedCommand", LoadedCommand);
I don't even know if I'm going about this the right way. I'm sort of diving into everything at once, with Prism and Dependency Injection and mvvm(with controllers) being relatively new to me.

Answer 1

I may not be entirely sure about your question. But the way I understand commanding in MVVM is: You have the view and instead of click events you use command objects.
The reason is, that click events go to the codebehind, and using command instead you have the ability to transfer the logic to the viewmodel.
The view uses binding to connect to the viewmodel.
So a short example:
(Usage):
<Element Property="{Binding PropertyNameInTheViewModel}" />
(Example):
<Button Command="{Binding ClickCommand}" />
Then of course make the View's datacontext to the viewmodel. Example (done in the codebehind):
public partial class View : Window
{
public View(ViewModel vm)
{
InitializeComponent();
this.DataContext = vm:
}
}
In the viewmodel
public ICommand ClickCommand { get; set; }
#region constructor
public Viewmodel()
{
ClickCommand = new DelegateCommand(ButtonClick);
}
#endregion
private void ButtonClick()
{
// handle the click
}
I'm not entirely sure what you mean by 'controller'. The design pattern as I've learned, goes View -> ViewModel -> Model. And use dependency injection in to the view constructor in order to pass the viewmodel. Personally I'm learning MEF (Managed Extensibility Framework) instead of Unity.