Snack Pack | The New Xamarin Android Device Manager
Description
This week, James is joined yet again by friend of the show Matthew Soucoup, who shows us how to extend the built-in capabilities of any View in Xamarin.Forms with little gems of awesomeness known as Behaviors. Matt demonstrates what a Behavior is, and how these reusable classes can expand the Xamarin.Forms controls functionality without having to subclass controls or modify the code-behind files.
Show Links:
- Code used in show
- Documentation: Xamarin.Forms Behaviors
- Reusable Command to Action Behavior
- Find James on: Twitter, GitHub, Blog, and his weekly development podcast Merge Conflict.
- Follow @JamesMontemagno
- Never Miss an Episode: Follow @TheXamarinShow
- Find Matt on Twitter, GitHub, and his Blog
Share
Download
More episodes in this series
Custom Vision – Machine Learning Made Easy with Jim Bennett
Related episodes
Translating Mobile Apps With The Multilingual App Toolkit with Cameron Lerum
Snack Pack 25: New .NET Standard Mobile App Templates in Visual Studio 2017
Episode 32: What's new in Xamarin.Forms 2.4 with David Ortinau
Episode 30: Xamarin University Training with Adrian Stevens
Snack Pack 15: Upgrading to Xamarin.Forms to .NET Standard
Episode 13: MVVM Helpers
Monitor Your App's Health with App Center Analytics & Crash
Azure Active Directory B2C Authentication For Mobile with Matthew Soucoup
Building the New MSN News App with Xamarin
Continuous Delivery Everywhere with App Center Distribute | The Xamarin Show
The Discussion
-
Me Ask You You beard makes you look like Yusuf Islam. No pun intended.
-
CodeGrue How do Behaviors differ from Effects? They seem very similar.
-
MattSoucoup @CodeGrue:They are very similar, both used to add additional features!
You generally use an Effect for a small styling/UI change to a control. And the change you want to make has to be done in a platform specific way.
Behaviors on the other hand are extending the functionality of the control - like adding validation. And the functionality that you're adding does not need to tap into anything platform specific.
Quick way to keep them straight ... Effects=UI ... Behaviors=Functionality.