The Wooden Moose .NET Blog
366 FOLLOWERS
The Wooden Moose .NET Blog explains UWP and Xamarin.
The Wooden Moose .NET Blog
2y ago
After almost a year of hard work, I am very excited to announce Fabulous 2.0!
This new release is a complete rewrite of Fabulous, focusing on performance and developer experience.
Version 2.0 is the first of several major releases.
It comes with a brand new DSL inspired by SwiftUI and improved performance to ensure the best possible development experience.
In later releases, we will introduce support for MAUI and support for components to help you scale your apps with ease.
If you’re interested, you can read more about it here: Reasonable goals of v2
I want to thank all Fabulous contributors f ..read more
The Wooden Moose .NET Blog
5y ago
It’s the 21st day of the F# Advent Calendar 2019, only 4 days left before Christmas!
If this year, like all the previous ones, you wrote Santa asking him to bring a new framework finally letting you write apps you’ll love, with a clean, easy-to-use, reliable, maintainable and testable architecture, your present has come early!
Today, we will see together what Fabulous is, what it offers, and how it helps you build apps that you will finally be proud of.
F# and the MVU architecture
Recently, frameworks like Elm, React-Redux and Flutter became really popular thanks in part to their alternati ..read more
The Wooden Moose .NET Blog
5y ago
The full sample can be found on Github : https://github.com/TimLariviere/Sample-FSharp-AzureCosmosDb
Setting up a graph database is really easy thanks to Azure Cosmos DB. Azure Cosmos DB is a multi-model database hosted on Microsoft Azure with lots of cool features such as a Graph API (with support for the popular Gremlin language) and turn-key worldwide distribution. For more information on Azure Cosmos DB, head to the documentation.
In this post, I will show you how to make a .NET Core app written in F# that will use the Graph API of Azure Cosmos DB.
Azure Cosmos DB Graph SDK
Microsoft m ..read more
The Wooden Moose .NET Blog
5y ago
After deploying your beloved Azure Function written in F#, you might end up with the following exception when executing the function: Could not load file or assembly 'FSharp.Core, Version=4.4.3.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies
But why such an exception? When running the function locally, all was fine.
That’s because when Azure runs your function, it runs it inside a process that is already using an older version of FSharp.Core. And when it tries to load the FSharp.Core.dll from the /bin folder, it fails. The F# Core Engineering team warns us abo ..read more
The Wooden Moose .NET Blog
5y ago
Following the previous post on Google authentication, I will now focus on how to authenticate on Facebook with Xamarin.Auth and retrieve the user’s email address. In case you missed the Google post, you can read all about it here: Authenticate users through Google with Xamarin.Auth
As previously, a sample is available on GitHub: https://github.com/TimLariviere/Sample-XamarinAuth-Facebook
Facebook authentication with Xamarin.Auth
Unlike Google, Facebook doesn’t require us to use native SDKs to authenticate users. So we can let the IsUsingNativeUI flag of Xamarin.Auth disabled, which is hopef ..read more
The Wooden Moose .NET Blog
5y ago
I’ve recently worked on a Xamarin app that needed to authenticate its users against Facebook, Google, and Twitter, and needed to retrieve their email addresses. Xamarin.Auth did the heavy lifting for us, handling all the OAuth authentication flow. But configuring it for Facebook, Google, and Twitter can be complicated as their configurations are (not so) slightly different.
After quite a bit of struggle, I decided to share every single steps that led me to successfully implement authentication and getting the user’s email address.
In this post, I will focus on integrating Google authenticati ..read more
The Wooden Moose .NET Blog
5y ago
Welcome in this long awaited part 2 of the serie “One Mac. Small Xamarin team. How to.”.
In part 1, we saw what possibilities in terms of hardware are available when developing for iOS with Xamarin (if you missed it, it’s still time to read it).
Today, I will explain how to leverage a single Mac for a small team, and how to enable simultaneous debugging between developers. This post is applicable to every Mac machines. A good candidate for such a setup would be either a Mac mini or a Mac Pro.
I won’t go into details about developer certificates and provisioning profiles.
Contents:
The Ma ..read more
The Wooden Moose .NET Blog
5y ago
When we talk about mobile apps, a web API is generally hiding in the background, doing most of the work like connecting to a database, verifying authorization, computing data, and so on. Like everything else, those APIs need protection against unauthorized calls that don’t come from our mobile apps.
In this post, I will explain how to leverage Azure Active Directory to protect our WebAPI without any code, and how to call this WebAPI from our mobile apps.
So, how do we do that?
In order, we will :
Enable Azure AD authentication on our API
Declare our apps in the Azure AD in order to allow ..read more
The Wooden Moose .NET Blog
5y ago
A few warnings before we begin :
This post is only about Visual Studio 2015. In Visual Studio 2017, you can find the option “Hide from Solution Explorer” in the context menu.
Also this post is only about xproj-based projects. It applies to .NET Core libs and apps like ASP.NET Core. The next version of .NET Core (2.0) will revert back to csproj files.
Unlike csproj-based projects where files need to be referenced in the csproj, with xproj-based projects Visual Studio will list by default every files in the project folder in the Solution Explorer.
To avoid cluttering your Solution Explorer w ..read more
The Wooden Moose .NET Blog
5y ago
When targeting iOS, whichever technology you choose (ObjC/Swift, Cordova, Xamarin, etc.), Apple requires you to build your application on a physical Mac machine. Running MacOS in a virtual machine on a non-Apple machine is not an option, as it is forbidden by Apple.
In this serie, we will look at the available options for a small team of Xamarin developers (up to 5 devs). This post is a brief look at the possibilities offered to us in terms of hardware when developing for Xamarin. Then in the next two posts, we will take a deep dive at the last option, one Mac for a really small team, and how ..read more