This project has moved and is read-only. For the latest updates, please go here.

Is there going to be a new version of MVVM Light

Oct 26, 2010 at 1:36 PM

The last version was on April, 2010.

Is there going to be a new version or release soon, and is the MVVM Light framework or pattern will be supported and live .

It is neccessary that we don't use obsolete techniques

Thanks alot.


Oct 26, 2010 at 1:48 PM


MVVM Light is far from obsolete, in fact the components as they are available now are used in multiple apps both for Silverlight and WP7. The reason why no changes were made since April is that the components work great as they are. i plan to resume working on MVVM Light because I completed my book Silverlight 4 Unleashed, and i have more time to work on ideas that i have around MVVM light, but I am not planning to change the existing components all too much, because there is not a need.



Oct 26, 2010 at 1:53 PM
Edited Oct 26, 2010 at 1:54 PM

Thank you for your quick reply,

I read somewhere that there will be a change to the viewmodel locator in MVVM Light, that would be easier and takes less code. (May be using MEF)

is this right?


Oct 27, 2010 at 9:44 AM

"The components work great as they are"

It's true, except the little bug explained at the end of this thread ;-) : 

Oct 27, 2010 at 11:53 AM


we could argue if this is a bug or not. Standard commands are also not evaluated when the attached element is disabled.

nitpicking:end ;-)

That said, I agree that your proposal to add such a property is interesting and I will definitely consider it for V4

And yes, I will resume work on MVVM Light shortly :-)



Oct 29, 2010 at 11:15 AM
Edited Oct 29, 2010 at 1:41 PM

In my point of view, when we use an EventToCommand, we expect that the corresponding command will be evaluated each time the event is raised.
But, I understand that in some cases (exceptionally, I think), it could be nice to not evaluate this command when the element is disabled.


Oct 29, 2010 at 11:09 PM

Would you accept it if it was the other way round? I.e. the default is that disabled elements do not execute the command, and there is a property that changes this behavior?

The advantage is that it wouldn't be a breaking change. Plus, it would be compatible with the way that the Command property behaves in SL4. This way, you can easily handle a command in WP7 projects, where the Command property is missing, with exactly the same behavior.



Nov 2, 2010 at 10:39 AM

Yes, I think it's acceptable, you are right.