In case you missed the big news, the XAML Behaviors are now open source in GitHub and available to use in UWP, both in managed and native apps, mostly due to the work of some awesome MVPs!
They were kind enough to keep me in the loop and that allowed me to prepare for the incoming changes! ;)
Cimbalino Toolkit 2.1.0
Version 2.1.0 of the Cimbalino Toolkit is a basic update of the toolkit with a few improvements and bug fixes, but takes into account the new XAML Behaviors:
- UWP apps it now will pull the XAML Behaviors Managed NuGet package to the projects
- non-UWP apps will still use the NuGet PowerShell scripts to add the Behaviors SDK
A few weeks ago I introduced the
MonitoredInteraction class from Cimbalino Toolkit 2.0.0 to “prevent memory leaks in behaviors”, and I’m happy to say that those changes made it’s way to the XAML Behaviors code! :)
Do notice that while the
Interaction class in the XAML Behaviors now performs the proper attach/detach pattern, the same can’t be said for the Behaviors SDK Extension for non-UWP apps, so I strongly advise you to keep using the
MonitoredInteraction class for those projects!
One final note: if you actually want to use the XAML Behaviours, you will have to actually manually add the NuGet package to your project… this is due to the new Transitive Dependencies feature of NuGet 3.x, and as far as I know, there is no way of going around this extra step!