Merge Conflict
Merge Conflict 81: It Takes Two to Debug
When something goes wrong, it is time to debug! Or maybe first we should write logs? Maybe we should use the intermediate window? Or perhaps write a unit test? We discuss our pro tips for debugging when something goes wrong.
We also take a quick detour and talk about the cute Mini-Husky that James is dog sitting!
SUPPORT US ON PATREON: patreon.com/mergeconflictfm
Follow Us
- Frank: Twitter, Blog, GitHub
 - James: Twitter, Blog, GitHub
 - Music : Amethyst Seer - Citrine by Adventureface
 - Proudly recorded on Zencastr
 
Special Thanks
Thank you so much for our new Patreon supporters: Tyler, Bob, Matthew R, Matthew B, Brandon, Keven, Jonathan, Aden, Daniel!
Sponsored By:
- Syncfusion: Syncfusion offers the largest selection of controls for Xamarin.iOS, Xamarin.Android, and Xamarin.Forms. Check out our components on NuGet and don’t forget to download our Xamarin e-books. 
 
Links:
- P E N N Y • P I C K L E S (@penelopepicklesthedog) • Instagram photos and videos
 - Alaskan Klee Kai - Wikipedia
 - Serilog — simple .NET logging with fully-structured events
 - Debug Class (System.Diagnostics)
 - Console.WriteLine Method (System)
 - NLog
 - Managing Exceptions with the Debugger
 - Debugging with Xamarin | Microsoft Docs
 - Running Xamarin.iOS Unit Tests in Visual Studio Team Services | Xamarin Blog
 - Touch.Unit Automation Revisited | take a bit, get a byte
 
Merge Conflict