ViewModelLocationProvider should use DI instead of Reflection to create instances

[karlfl]

I stumbled across this when trying to fit my MEF samples to the Prism 6.0 code base using the ViewModelLocator.AutoWireViewModel . I have a single [ImportingConstructor] for my View Model with one parameter (my business service), but the ViewModelLocationProvider is using Reflection to get the View Model instantiating it with the default constructor. Therefore when the module attempts to display my view, I get this exception. "No parameterless constructor defined for this object." Should the ViewModelLocationProvider be using DI to get the View Model instance instead of Reflection?

[brianlagunas]

BY default, the VML does not use DI, because that would be creating a dependency on a specific Container that you may not want to be using. So, by default we use reflection. But, if you want o use DI, then you can easily use your own container of choice by overriding the SetDefaultViewModelFactory method. So if you want to use MEF, you can.

See this post: http://brianlagunas.com/getting-started-prisms-new-viewmodellocator/

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.