FreshMvvm 1.0 Released

So it’s official, FreshMvvm is now 1.0 and available in nuget.

Let’s take a look at some of the new features.

  • Ability to use ViewModel naming instead of PageModel, thanks to this contribution by Olexandr Leuschenko
  • Multiple Navigation Services
  • Support for custom IOC containers
  • Ability to Push a NavigationContainer
  • It also handles async better thanks to Olexandr Leuschenko

Let’s take a look at some of the bigger features in the release.

Multiple Navigation Services

It’s always been possible to do any type of navigation in FreshMvvm, with custom or advanced scenarios were done by implementing a custom navigation service. Even with this ability people found it a little hard to do advanced navigation scenarios in FreshMvvm. After I reviewed all the support questions that came in for FreshMvvm I found that the basic issue people had was they wanted to be able to use our built in navigation containers multiple times, two primary examples are 1) within a master detail having a navigation stack in a master and another in the detail 2) The ability to push modally with a new navigation container. In order to support both these scenarios I concluded that the FreshMvvm required the ability to have named NavigationServices so that we could support multiple NavigationService’s.

Using multiple navigation containers

Below we’re running two navigation stacks, in a single MasterDetail.

PushModally with new navigation stack

Custom IOC Container

The second major request for FreshMvvm 1.0 was to allow custom IOC containers. In the case that your application already has a container that you want to leverage.

Using a custom IOC container is very simple in that you only need to implement a single interface.

And then set the IOC container in the System.

This release can be found in nuget and the source code on github.



Leave a Reply