In today’s article, I will discuss some of the essential improvements of Prism 7 for Xamarin as well as the minimum steps to get you up and running using Prism 7 in Xamarin forms, so let’s get started.
.NET Standard Support
The long awaited .NET support for prism has arrived. It was during the 6.3 version days that I was having some problems with PCL projects wherein the more profiles that you select the less .NET APIs you can use but nevertheless .NET Standard will save the day.
In today’s article, I will discuss how to use the File System of Xamarin forms in data storage. File System storage is a great option for you if you want to store a more larger data in the file system, maybe in the form of XML or JSON file, if Preference storage is not enough for you and Database is an overkill for you.
In today’s article, I will discuss how to use the Preference in storing data. Preference is one of the different data storage strategies that Xamarin provides. It is primarily used to store small amount of data like user settings of your Mobile Application. The preference is a key value pair structure where it can only cater to simple or intrinsic data types (e.g. strings, int, bool).
For the last part of this Getting started Xamarin with Prism series, I would like to discuss about using Messaging in Xamarin forms. We will use our previous project from ourPart3of the getting started series and here is the link for the Repository:https://github.com/KirkPatrickJunsay/XamarinPrismSample
For the third part of this Getting started Xamarin with Prism series, I would like to discuss about using Navigation in Xamarin forms. We will use our previous project from our Part2 of the getting started series and here is the link for the Repository:https://github.com/KirkPatrickJunsay/XamarinPrismSample
We always hear the word Interface when we are creating Systems whether it be in Java or C# language. We all know that Interfaces are just binding contracts between two different entity or Classes. Another reason to implement Interfaces is too have a more decoupledsystem or a more cleaner Separation of Concerns. But sometimes like me, has a hard time grasping the true value of Interfaces in creating a program.
In today’s article I would like to briefly discuss one of the commonly used design pattern in software engineering which is Singleton Pattern. Singleton pattern is usually being used if you are creating a system that only needs one instance of a class and that instance will be used throughout the lifecycle of the application. Common scenarios of using Singleton pattern is for logging, database access, etc.