CodePlexProject Hosting for Open Source Software
MEFedMVVM should be splitted into 2 part: core and MVVM implementation.
I use Prism, I don't need DelegateCommand, Mediator, NotifyPropertyChangedBase and so on.
I totally agree, in fact this is something that I always wanted to change yet because of backward compatibility I am afraid of touching.
As I understand, it is possible to split it to two assemblies, isn't it?
And is it possible to use the same name for SL and WPF assemblies?
It is... and I will be doing this change very soon
What was the idea of referencing some code files in SL project from common project and some from WPF project?
Are you sure you want to delete this post? You will not be able to recover it later.
Are you sure you want to delete this thread? You will not be able to recover it later.