Announcing MVVM Light V5 for Windows and Xamarin

.NET, Blend, MVVM, Phone, Silverlight, Technical stuff, Visual Studio, Windows 8, Windows Phone, Work, WPF, Xamarin, XAML
53 Comments

Here at the Xamarin Evolve conference in Atlanta, I just announced the immediate availability of MVVM Light V5. This version runs on the following platforms:

  • Windows Presentation Foundation (3.5, 4, 4.5, 4.5.1)
  • Silverlight (4 and 5)
  • Windows Phone (7.1, 8, 8.1 Silverlight, 8.1 RT)
  • Windows Store (8, 8.1)
  • Xamarin Android
  • Xamarin iOS
  • Xamarin Forms


What’s new?

There are three major changes in this version: Xamarin Support, NavigationService and DialogService, and Portable Class Library support.

Xamarin support

This is the big news that I announced and demoed at Evolve. The new MVVM Light contains the following improvements for Xamarin

  • Binding framework for Xamarin Android and Xamarin iOS
  • Commanding framework for Xamarin Android and Xamarin iOS
  • ObservableAdapter for Xamarin Android
  • ObservableController for Xamarin iOS

Expect a lot more information about these additions in future blog posts. While you are waiting, you can download and try my Xamarin Evolve code sample (zip file). You can also browse the source code (Codeplex / Samples / Flowers).

Of course MVVM Light also works out of the box with with Xamarin Forms as shown in the sample application above.

NavigationService and DialogService

In V5, I decided to include two classes that I had been using in most of my applications. It is a cross-platform INavigationService and IDialogService interfaces with corresponding implementations on supported platforms.

The INavigationService provides a cross-platform navigation mechanism (including passing a parameter to the target page). It supports a CurrentPageKey property as well the the NavigateTo (with or without parameter) and GoBack methods.

I will provide more information about these two interfaces and their respective implementation in future blog posts. In the meantime, you can use my Xamarin Evolve code sample (zip file) to see how these classes are used in Xamarin Android, Xamarin iOS and Windows Phone (Silverlight) 8.1.

In V5, you get an implementation of these two classes on the following platforms:

  • Xamarin Android
  • Xamarin iOS
  • Windows 8 and 8.1
  • Windows Phone (RT) 8.1
  • Windows Phone (Silverlight) 8.0
  • Windows Phone (Silverlight) 8.1

In other platforms, the INavigationService and IDialogService interfaces are also available, but I didn’t provide an implementation. Notably in Windows Presentation Foundation, there is not standard navigation mechanism. For this reason, even though you can of course implement your own INavigationService, I am not providing a standard class for that.

Portable class library implementation

For a long time, there were three different Nuget packages for MVVM Light: The most popular one is the “MVVM Light Libs Only” package. There is also an “MVVM Light” package and an “MVVM Light Libraries Only (PCL)” package.

In V5 however, both the “Libs Only” packages are one and the same. I am keeping the (PCL) one around a little longer to allow people to upgrade smoothly, but it is the same package all over.

For people who were using the “non-PCL” package before, this means a few changes. Most importantly, there is now a new DLL added in some places, called GalaSoft.MvvmLight.Platform.DLL. This new DLL contains some platform specific code, notably the DispatcherHelper, NavigationService and DialogService classes.

Some non-PCL remains

For technical reason, I cannot provide a PCL version for all supported frameworks, because some are mutually exclusive. The following table shows in detail how the packages are built:

Framework Assemblies PCL or not?
WPF 3.5 GalaSoft.MvvmLight
GalaSoft.MvvmLight.Extras
Microsoft.Practices.ServiceLocation
System.Windows.Interactivity
No
WPF4 GalaSoft.MvvmLight
GalaSoft.MvvmLight.Extras
Microsoft.Practices.ServiceLocation
System.Windows.Interactivity
No
WPF4.5 (and 4.5.1) GalaSoft.MvvmLight
GalaSoft.MvvmLight.Extras
GalaSoft.MvvmLight.Platform
Microsoft.Practices.ServiceLocation
System.Windows.Interactivity
Yes
Silverlight 4
(see note 3)
GalaSoft.MvvmLight
GalaSoft.MvvmLight.Extras
Microsoft.Practices.ServiceLocation
System.Windows.Interactivity
No
Silverlight 5
(see note 3)
GalaSoft.MvvmLight
GalaSoft.MvvmLight.Extras
Microsoft.Practices.ServiceLocation
System.Windows.Interactivity
No
Windows Phone 7.1
(see note 3)
GalaSoft.MvvmLight
GalaSoft.MvvmLight.Extras
Microsoft.Practices.ServiceLocation
System.Windows.Interactivity
No
Windows Phone (Silverlight) 8 GalaSoft.MvvmLight
GalaSoft.MvvmLight.Extras
GalaSoft.MvvmLight.Platform
Microsoft.Practices.ServiceLocation
System.Windows.Interactivity
Yes
Windows Phone (Silverlight) 8.1 GalaSoft.MvvmLight
GalaSoft.MvvmLight.Extras
GalaSoft.MvvmLight.Platform
Microsoft.Practices.ServiceLocation
System.Windows.Interactivity
Yes
Windows Phone (RT) 8.1
(see note 1)
GalaSoft.MvvmLight
GalaSoft.MvvmLight.Extras
GalaSoft.MvvmLight.Platform
Microsoft.Practices.ServiceLocation
Yes
Windows Store (RT) 8 and 8.1 GalaSoft.MvvmLight
GalaSoft.MvvmLight.Extras
GalaSoft.MvvmLight.Platform
Microsoft.Practices.ServiceLocation
Yes
Xamarin Android GalaSoft.MvvmLight
GalaSoft.MvvmLight.Extras
GalaSoft.MvvmLight.Platform
Microsoft.Practices.ServiceLocation
Yes
Xamarin iOS GalaSoft.MvvmLight
GalaSoft.MvvmLight.Extras
GalaSoft.MvvmLight.Platform
Microsoft.Practices.ServiceLocation
Yes
PCL (for class libraries)
(see note 2)
GalaSoft.MvvmLight
GalaSoft.MvvmLight.Extras
Microsoft.Practices.ServiceLocation
Yes

NOTES

Microsoft.Practices.ServiceLocation is added through a reference to the CommonServiceLocator Nuget package by Microsoft Patterns and Practices.

For the PCL versions, the GalaSoft.MvvmLight and GalaSoft.MvvmLight.Extras assemblies are the same binary file.

Note 1: This version doesn’t include EventToCommand, please use InvokeCommandAction instead.

Note 2: This version is what you get when you add MVVM Light to a Xamarin Forms application. This package is also used when you add MVVM Light support to a satellite portable class library used in your application.

Note 3: Legacy support; some new features might not be available.

Installation

As of now, you can install MVVM Light V5 in your applications.

With Nuget:

  • MVVM Light Libraries Only
  • MVVM Light (with ViewModelLocator and MainViewModel)

If you are upgrading an existing application, I recommend removing the old Nuget package first and then re-adding the new Nuget package. You will probably have to update a few references and “using” directives but it shouldn’t be too painful.

Visual Studio Extension (includes Code snippets and Templates)

Available at this address (Visual Studio 2012 | Visual Studio 2013), or through the “Tools / Extensions and Updates” menu. I recommend uninstalling the old MVVM Light package first, and then installing the new one.

I hope that these improvements will help you build amazing applications! Of course, I always welcome your feedback.

Happy coding
Laurent

GalaSoft Laurent Bugnion
Laurent Bugnion (GalaSoft)
Share on Facebook
 

53 Responses to “Announcing MVVM Light V5 for Windows and Xamarin”

  1. MVVM LightがXamarinをサポート | かるあのメモ on WordPress Says:

    […] Announcing MVVM Light V5 for Windows and Xamarinより。 […]

  2. Keynote Xamarin Evolve 2014 : quelles nouveautés ? | Soat blog Says:

    […] MVVM Light Toolkit, a profité de l’évènement et de sa conférence pour annoncer une nouvelle version supportant […]

  3. Mike C Says:

    I’ve been ignoring MVVM Light long enough: where is the best resource for learning this if I’ve never done XAML before?

  4. lbugnion Says:

    Hi,

    If you have a Pluralsight subscription or don’t mind getting one, this is the best place to get started, checking my course http://galasoft.ch/s/psmvvm1

    If you don’t want that, I recommend my series on MVVM Light in MSDN magazine at http://galasoft.ch/s/msdn.

    Have fun!
    Laurent

  5. Daniel Madsen Says:

    Thank you for adding support for Xamarin.Forms, looking forward to studying the example code :)

    I was hoping to catch your session yesterday on the Xamarin Evolve live stream, but sadly they only broadcasted the center stage :( Will your session be provided later online?

  6. lbugnion Says:

    Hi,

    Happy you’re excited :)

    The session was filmed so I fully expect it will be online soon. Stay tuned to my blog for more info.

    Cheers
    Laurent

  7. Adam J Wolf Says:

    Hey Laurent, I just added this post to the http://www.XamarinWeekly.com newsletter issue #9. It comes out tomorrow the 10th.

    I am looking forward to more articles about using MVVM Light with Xamarin Forms. I’ll have to check out your Pluralsight course. Have you thought about producing a Pluralsight course with Xamarin Forms and MVVM Light? One can hope. Adam

  8. Edison Capiz Says:

    Hi Laurent,

    Thank you for your updates.
    I have a MVVMLight WPF4.5 app and upgraded it to v5 and I got some build errors.
    It would seem, you have removed RaisePropertyChanging() from ViewModelBase()?

    Also, EventToCommand in the XAML is no longer recognized.
    I was able to fix it by adding
    xmlns:z=”clr-namespace:GalaSoft.MvvmLight.Command;assembly=GalaSoft.MvvmLight”
    xmlns:cmd=”http://www.galasoft.ch/mvvmlight”

    But I don’t know if this is the correct way to do it.

    Thank you so much!

    -Edison

  9. lbugnion Says:

    Hi,

    Thanks! Yes such a course is definitely something i would like to do soon.

    cheers
    Laurent

  10. lbugnion Says:

    Sorry about the issues you had. I will study that more closely and give you a more detailed reply.

    cheers
    Laurent

  11. The Morning Brew - Chris Alcock » The Morning Brew #1713 Says:

    […] Announcing MVVM Light V5 for Windows and Xamarin – Laurent Bugnion announces the latest release of MVVM Light , with an incredible array of platfoms now supported this really is a run anywhere framework. […]

  12. INavigationService in MVVM Light V5 | Around and About .NET World Says:

    […] days ago, at Xamarin Evolve conference in Atlanta, has been announced the availability of MVVM Light V5. This release contains interesting updates for Xamarin, as we can read in the official blog […]

  13. NavigationService in MVVM Light V5 | Around and About .NET World Says:

    […] days ago, at Xamarin Evolve conference in Atlanta, has been announced the availability of MVVM Light V5. This release contains interesting updates for Xamarin, as we can read in the official blog […]

  14. Jeffry van de Vuurst Says:

    Hi Laurent,

    Great new release! I seem to have one issue, the sample Flowers solution that you provide works on Android, but on iOS I just see an empty list.

    Then I created my own sample project and TwoWay binding on a UITextField does not work. TwoWay binding on an Android EditText does work.

    I can send you an example project if you want.

  15. lbugnion Says:

    Hi,

    Thanks for the feedback. I will check it out.

    Yes please send me a repro. Please note that you need to save the created binding (the return value of SetBinding) in an attribute if you want it to work on iOS. The binding instance is using weak references, and the GC on iOS is a bit too aggressive and collects it immediately. The issue is not on Android, so maybe this is what you are observing. I plan to blog about this and a few more things in the next few days/weeks.

    Cheers
    Laurent

  16. Lindermann's Blog | Announcing MVVM Light V5 for Windows and Xamarin Says:

    […] http://blog.galasoft.ch/posts/2014/10/announcing-mvvm-light-v5-for-windows-and-xamarin/?utm_source=f… […]

  17. Jeffry van de Vuurst Says:

    Hi Laurent,

    Where can I send my repro to? I’m saving the return of the SetBinding to a public property.

  18. lbugnion Says:

    Please send to Laurent at galasoft dot ch, thanks!

  19. DialogService in MVVM Light V5 | Around and About .NET World Says:

    […] days ago we talked about the new release of MVVM Light Toolkit and, in particular, we presented the new […]

  20. Jeffry van de Vuurst Says:

    Hi Laurent,

    By looking at your source code we figured out that we could get the twoway binding to work on iOS using this code:
    _serverUrlBinding = this.SetBinding(() => Vm.ServerUrl, () => TextServerUrl.Text, BindingMode.TwoWay).UpdateTargetTrigger(“EditingChanged”);

    However, I’m not sure this is expected behavior. This code is not needed on Android.

  21. Announcing MVVM Light V5 for Windows and Xamarin Says:

    […] , windev , windows-phone , wpdev , laurent-bugnion Read original post by Laurent Bugnion at GalaSoft BlogHere at the Xamarin Evolve conference in Atlanta, I just announced the immediate availability of […]

  22. Rob Pijnenburg Says:

    Hey,

    Looks like the update broke my CanExecute of the RelayCommand is this possible?
    Awseme work further on!

  23. lbugnion Says:

    Hi,

    There is an issue with RelayCommand.CanExecute in WPF if you rely on the CommandManager to handle the CanExecuteChanged. I am working on a fix. In the meantime, please revert to V4.4. Sorry for the inconvenience.

    More details at https://mvvmlight.codeplex.com/workitem/7659

    Cheers
    Laurent

  24. Scott Smith Says:

    Is there an implementation of IDialogService and INavigationService for Xamarin.Forms in the NuGet packages? I know there was in the sample code from your talk. Just wondering if you have included them in the binaries. Great talk by the way!

  25. Sergio Says:

    Hi Laurent,

    First of all congratulation for the awesome work!

    I’m currently developing a Xamarin.Forms app and I’d like your opinion on something.
    I’m using Xamarin.Forms.Labs (https://github.com/XLabs/Xamarin-Forms-Labs) mostly for cross-device feature capabilities (i.e. Take picture). They appear to have a custom implementation of MVVM (ViewFactory, ViewModel, …) which is within their *core* nuget library. Since I need to use the library for the above-mentioned features, should I use their MVVM implementation? Why not reach them and see if you can collaborate (i.e. integrate MVVM light in their library)?

    Cheers

    Sergio

  26. lbugnion Says:

    Hi,

    I was asked the same question at Evolve after my session. My take on that is that the integrated MVVM classes in Xamarin Forms fulfill the same kind of purpose than the ones that you get in Microsoft XAML projects when you create a new app using some of their templates. For me, it is kind of the “gateway drug” to MVVM, some classes provided to make the user aware of the pattern and make him curious about it. I don’t see many production projects using the Microsoft MVVM classes though and I suspect that once the initial curiosity is satisfied, developers are quickly moving to a more established framework like MVVM Light, especially for the cross platform advantages.

    Cheers
    Laurent

  27. lbugnion Says:

    Hi,

    Right now, NuGet doesn’t allow me to differentiate a “classic” Xamarin Android/iOS project from a Xamarin Forms project. This is an issue I am trying to solve. For now, I recommend picking the files from the Evolve sample (http://1drv.ms/1yNA7qU) and integrating that in your app directly.

    Cheers
    Laurent

  28. lbugnion Says:

    Just want to make sure that you saw the V5.0.2 release which fixes the issue (make sure to observe the release notes at http://www.mvvmlight.net/installing/changes and especially the Important note about issue 7659).

    Cheers
    Laurent

  29. Klas Hammar Says:

    Hi,

    I have been using MVVM Light building Windows Phone 8 Apps and planned on getting started om Universal Apps (W8.1 & WP8.1). I installed MVVM Light V5.0.2 but I cannot find a project template for a Universal App. Is there a sample or guideline available somewhere?
    Thanx,
    Klas

  30. Klas Hammar Says:

    Hi,

    I have been using MVVM Light (V4) to build Windows Phone 8 Silverlight Apps (it’s a great toolkit!) and was planning to try building a universal app (Win 8.1 & WP8.1) with the new MVVM Ligh V5.
    But I’m a bit uncertain on how to set up the initial solution/Projects in VS2013 – I can only find references on how to do it with V4 and this does not utilize the new Navigation service etc. Are there any short pointers on on how to set up the structure?
    Thanx,
    Klas

  31. Pierre Says:

    Hi Laurent,
    I am new with xamarin and mvvm light, could you please give a hint from where can I start, any mvvmlight xamarin examples?
    I created 3 views and viewmodels but i don’t know how to go from view to view :(
    I appreciate any help
    thanks

  32. lbugnion Says:

    Hi,

    Start with my Evolve talk. Check the sample code. Come back to me if you have more questions.

    http://blog.galasoft.ch/posts/2014/10/my-xamarinevolve-talk-is-online-for-your-viewing-pleasure/

    Cheers
    Laurent

  33. Denis Says:

    Hello,

    I you going to move to Xamarin.iOS 64bit (Unified API). It is critical because

    Starting February 1st, 2015 Apple requires that all new iOS submissions to the App Store must be 64 bit applications built with the iOS 8 SDK; and from June 1st, 2015 app updates will also need to follow the same requirements. As a result, Xamarin.iOS applications will need to be migrated to the new Unified API instead of the existing Classic MonoTouch API to support 64 bit.

    http://developer.xamarin.com/guides/cross-platform/macios/unified/

    Thank you.

  34. lbugnion Says:

    Hey Denis,

    Working on it now.

    Thanks
    Laurent

  35. Anders Says:

    Hi Laurent,

    I watched your excellent talk on the Xamarin Evolve 2014, and it inspired me to take on MVVM on a new Xamarin.Forms app that needs to run on both Android and IOS.

    I need make our existing Silverlight 5 application run on Xamarin. The SL5 app allready uses Mvvm Light.

    So my idea is, to use a Portable Class Library that supports SL5, Xamarin Android, and Xamarin IOS. Then move all Model and ViewModels to the PCL, and install Mvvm Light in that PCL.

    But i get an error when installing MwwmLight into that PCL:
    Could not install package ‘Portable.MvvmLightLibs 5.0.2.0′. You are trying to install this package into a project that targets ‘portable-net45+sl50+win+wp80+MonoAndroid10+xamarinios10+MonoTouch10′, but the package does not contain any assembly references or content files that are compatible with that framework. For more information, contact the package author.

    Is it not possible for me to share the PCL with Mwwmlight to both Xamarin and Silverlight 5 projects?

    Kind Regards
    Anders

  36. Pierre-Christophe Says:

    Bonjour Laurent,

    Je m’excuse par avance pour mon commentaire qui fait un peu doublon avec un autre commentaire posté ici :
    http://blog.galasoft.ch/posts/2011/01/navigation-in-a-wp7-application-with-mvvm-light/

    Néanmoins je voudrais savoir quelle méthode tu conseilles pour l’implémentation de la navigation avec MVVM Light 5 et une application Universal Windows 8.1 / Windows Phone 8.1 ?

    J’ai lu cet article :
    https://marcominerva.wordpress.com/2014/10/10/navigationservice-in-mvvm-light-v5/

    Mais j’aurais besoin de pouvoir récupérer des paramètres lors de la navigation d’une page à l’autre (liste d’articles => détails d’un article, liste de contacts => détails d’un contact, …)

    Aurais-tu un exemple concret me décrivant cette implémentation?
    Ou conseilles-tu de faire cela en code behind?

    Tu parles d’un article sur le blog à venir, mais je n’ai rien trouvé…

    Merci d’avance,

  37. Windows Phone MVVM Light: NavigationService CanGoBack Says:

    […] Light is a simple yet powerful framework for developing apps, and with the latest version 5 includes a new cross-platform NavigationService to aid in abstracting the navigation component […]

  38. Windows Phone and MVVM Light: NavigationService and CanGoBack Says:

    […] Light is a simple yet powerful framework for developing apps, and with the latest version 5 includes a new cross-platform NavigationService to aid in abstracting the navigation component of […]

  39. Nigel Stratton Says:

    Hi Laurent,

    I’ve been using MVVMLight for a while, I just upgraded and found the old Messenger has been deprecated. You have a couple of MSDN atricles but I’m not sure how to implement DialogService. Do you have a simple Win 7 WPF example that shows how to display a DialogBox?

    Thanks,
    Nigel

  40. lbugnion Says:

    Hi,

    The Messenger is not deprecated. Only the DialogMessage. I am working on a series of articles on NavigationService and DialogService. I will blog about it, so stay tuned. In the meantime, feel free to continue using DialogMessage if you are comfortable with it.

    Cheers
    Laurent

  41. Mark Brown Says:

    Hi Laurent

    I’m trying to get NavigationService working with my Xamarin Forms Cross Platform project. I have a PCL with my shared code along with the three other projects for each platform.

    I have my ViewModelLocator etc etc. Are the above Navigation / Dialog additions compatible with Cross Platform Navigation? If so a few pointers would be appreciated, as I couldn’t get the above to work…

    At the moment I’m managing Navigation using the Messaging Service. Subscribing (constructor of the Xaml code behind) and Send messages (RelayCommand)

    Look forward to your reply.

    Thanks

    Mark

  42. Eldho Says:

    SimpleIoc.Default.GetInstance().NavigateTo(“topupdetails”,tappedItem);

    I have passed an object inside the navigation , but could get that object anywhere , I tried in OnNavigated but can’t figure how to retrieve it, Any way of getting this passed value to the navigated view model ?

  43. lbugnion Says:

    Hi,

    Which framework are you using?

    I am in the process of writing documentation about the NavService. Currently I have iOS ready, working on more (see http://www.mvvmlight.net/doc).

    Thanks
    Laurent

  44. J4N Says:

    Hi,

    I was pretty excited when I see that you were now introducing Navigation within the library, but could you give me a small example for a WPF application(Not silverlight?) Because for now I’m unable to make anything work.

  45. Deepak Says:

    Hi,

    I am using MVVMLight in xamarin Android project. I have created binding for control EditText as below
    editText.SetBinding(() => SourcrProperty, () => editText.ModifiedText, BindingMode.TwoWay);

    the above code works fine in Build mode of the solution but when i change to Release mode. I see the Below issue:

    throw exception with message “Eventhandler TextChanged:EvnetName not found”

    Need your help here. Why doesn’t it work in Release mode?

    Thanks
    Deepak

  46. Deepak Says:

    Updated Snippet:
    editText.SetBinding(() => SourcrProperty, () => editText.Text, BindingMode.TwoWay);

  47. lbugnion Says:

    Hi,

    This is because the linker on Xamarin platforms is quite aggressive and will remove the events that are not used. In a TwoWay binding on a TextView, the binding attempts to subscribe to the TextChanged event in order to update the source property. Unfortunately, because binding is based on reflection, the linker doesn’t notice that the TextChanged event is in fact used, and when using the Release mode, the event is removed in order to save space.

    You can solve this with two possible workarounds:

    1) (maybe not the best) in the project properties, under Android Options / Linker, select “None” for the Linking combobox. This will cause the application size to grow, however. Using these options, you could also remove linking for specific assemblies.

    2) You can subscribe for the event in your code to fool the linker into keeping the event. To do this, you need to add something like

    editText.TextChanged += (s, e) {}

    I will publish some documentation about that in the next few days.

    Cheers
    Laurent

  48. Eldho Abe Says:

    I’m using MvvmLight 5 , i love mvvm light , Thanks for making it Open .

    In my Wp 8.1 project i have implemented the INavigation Service, how do i clear the NavigationService stack , Or How can i disable to GoBack() when user press the hardware button. Is there any built-in way to do this ?

    Or shall i try something like this

    http://blog.falafel.com/windows-phone-and-mvvm-light-navigationservice-and-cangoback/

    void HardwareButtons_BackPressed(object sender, Windows.Phone.UI.Input.BackPressedEventArgs e)
    {
    var frame = Window.Current.Content as Frame;
    if (frame.CanGoBack)
    {
    var navigation = ServiceLocator.Current.GetInstance();
    navigation.GoBack();
    e.Handled = true;
    }
    }

  49. Windows Phone and MVVM Light: NavigationService and CanGoBack | Xamarin Fire Says:

    […] Light is a simple yet powerful framework for developing apps, and with the latest version 5 includes a new cross-platform NavigationService to aid in abstracting the navigation component of […]

  50. Windows Phone and MVVM Light: NavigationService and CanGoBack | SelArom Dot Net Says:

    […] Light is a simple yet powerful framework for developing apps, and with the latest version 5 includes a new cross-platform NavigationService to aid in abstracting the navigation component […]

  51. Using MVVM Light Toolkit with Windows 10: Getting Started Says:

    […] and ViewModelBase) into all projects as well as the platform-specific implementations (such as the NavigationService we’ll be looking at in a future post) into the Windows project. Any time you want to target […]

  52. Giap Tran Says:

    Hi Laurent,

    I have some issue for binding data in Xamarin Android.
    I have set binding data in HomeActivity (FragmentActivity) like:

    bindingLoginInVisible = this.SetBinding(() => HomeViewModel.IsLoginVisible) .WhenSourceChanges(UpdateLoginInVisible);

    In HomeViewModel, I call:
    RaisePropertyChanged(() => IsLoginVisible);
    But sometimes, I can’t receive data change in UpdateLoginInVisible.
    Althought, bindingLoginInVisible has exist and reference property IsLoginVisible and action UpdateLoginInVisible.

    This issue exist in another Activities. But, It work well in iOS.
    Could you support me resovle this issue?

    Thanks,
    Giap Tran

  53. lbugnion Says:

    Hi,

    Can you send me a repro? laurent at galasoft dot ch.

    Thanks
    Laurent

Leave a Reply