Publishing #MVVMLight V5.4.1 with .NET Standard support

.NET, .NET Standard, MVVM, Technical stuff, Universal Windows Platform UWP, Windows 10, Work, WPF, Xamarin

I just finally published MVVM Light V5.4.1 which is a stable version containing the .NET Standard support that was released as a preview a few months ago. It took a long time for this version to come out due to the new job keeping me busy as well as a few health issues in the family.

I am really happy to have this stable version out and about! Make sure to upgrade your packages! Pay attention to the following details:

Full list of changes

The change log is available here.

GitHub code repo

Since Codeplex is no more, I moved the code and everything else to Github.

.NET Standard

The details for .NET Standard support are detailed here, including how you can upgrade to this new version. Please note that MVVM Light for .NET Standard in a separate Nuget package named MvvmLightLibsStd10.


I am now supporting V2.0.2 of CommonServiceLocator. In this new version, the CommonServiceLocator developers decided to change the namespace. As a consequence, if you are upgrading, you must change the namespace section as follow:

// OLD
using Microsoft.Practices.ServiceLocation;

// NEW
using CommonServiceLocator;

Note that like before, and as mentioned here, the .NET Standard version of MVVM Light doesn’t not include the CommonServiceLocator dependency.

Thanks for your continued support to MVVM Light and Happy Coding!!

11 Responses to “Publishing #MVVMLight V5.4.1 with .NET Standard support”

  1. Alex Says:

    I just wanted to inform you that Mvvm light 5.4.1 contains a bug: Microsoft.Practices.ServiceLocation is missing and thus the installation does not work. Version 5.3 works fine.

  2. lbugnion Says:

    Hi, can you give me more details? I tested the installation extensively and never noticed an issue. Note that the Service Location is not available in the. Net standard version, as documented at

  3. Andrew Says:

    Agreed with Alex. Not working.

  4. Andrew Says:

    Line: ServiceLocation.ServiceLocator.SetLocatorProvider(() => SimpleIoc.Default); prevents compile

  5. Andrew Says:

    CHanged to CommonServiceLocator.ServiceLocator.SetLocatorProvider(() => SimpleIoc.Default); which removed error warning from .cs file. HOwever won’t compile App.xaml “Could not load file or assembly ‘Microsoft.Practices.ServiceLocation, Version=″

  6. Rob Says:

    Just need to delete obj and bin folders, then do a clean and rebuild to fix Andrew’s issue above.

  7. Terje Says:

    No code snippets are installed with the extension installer.

  8. Buda Florin Says:

    Laurent, please make a popup or something to be sure you inform about CommonServiceLocator. I assumed too that it’s a mvvmlight’s bug.

  9. lbugnion Says:

    Where would you want to see the pop-up? When you install the Nugget package?

  10. Robert Stefanz Says:

    If you update from 5.3 to 5.4, you just get an error about CommonServiceLocator. If you try to solve the problem by your self, it could happen that you overwrite the Locator file and the ViewModel, if you update you should never overwrite the files without a copy of this files after Update you should directed to this homepage to read about the errors

  11. lbugnion Says:

    Hi, this is documented here: . Unfortunately the ComonServiceLocator team decided to change their namespace, which is a breaking change. Very annoying, I agree.

Leave a Reply