This article is part of a series called Playground: Playground – Part 1: A Xamarin.Forms Microsoft.Extended journey Playground – Part 2: Settings with Options pattern Playground – Part 3: Catch it, trace it, log it and upload it (this one) In the previous article, we implemented our settings layer. In this one, we’ll add some logging capabilities to our Playground. As Shiny comes with its own logging system built in, I was wondering if official Microsoft.Extensions.Logging packages could add some more value or not. Actually, not so much as it adds a lot more package dependencies for almost the same job offered by Shiny.Core’s logging system. Also, if Shiny’s ILogger interface offers the opportunity to save some more key/value parameters while tracking events and exceptions, it’s not available into the extension one AFAIK. So, if we’ll use a built-in feature, why this article? Because I want more 🙂 First of…
prism
This article is part of a series called Playground: Playground – Part 1: A Xamarin.Forms Microsoft.Extended journey Playground – Part 2: Settings with Options pattern (this one) Playground – Part 3: Catch it, trace it, log it and upload it In the previous article, I created an empty project with Xamarin.Forms, Prism, Shiny and ReactiveUI all wired together. Now, one of the first thing we do need is managing settings. As we get access to IServiceCollection in our Xamarin.Forms app thanks to Prism and Shiny, the door is wide open to use any extensions available for it. One of those are Microsoft.Extensions.Options and Microsoft.Extensions.Configuration. We’ll try to find out how it could be useful for settings management.
This article is part of a series called Playground: Playground – Part 1: A Xamarin.Forms Microsoft.Extended journey (this one) Playground – Part 2: Settings with Options pattern Playground – Part 3: Catch it, trace it, log it and upload it Into this Playground blog post series, I’ll try to experiment some concepts, frameworks and plugins, to find out how it could be useful to build a base project. A project that could be a good starting point for further customer specific mobile developments. You know we are talking here about this famous templating project we probably all try to create, reshape, and trash and again and again like almost every year. So this one should be the one? Well it’s not the point actually. I just like to play with all exiting stuff coming from the open source community like Xamarin.Forms, Prism or Shiny, and my base target is to…