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.
For the second part of this Getting started Xamarin with Prism series, I would like to discuss on how to use Command in Xamarin forms. By the way if you missed the Part 1 of this series you can check this article.
When you say Command, for example in Win Forms it’s just an event that was fired
due to let’s say a button click or an event brought by textbox lost/on focus but in Xamarin
Commands are just methods that are directly binded from your view e.g. (Button, MenuItem, ToolbarItem) and executes the binded method in your ViewModel.
In today’s article I will discuss about the basic requirements you need to perform for running Xamarin Forms with Prism 6 framework. So what is Prism by the way, Prism is a framework which originated as a XAML application framework mainly during the early days of WPF. It was previously maintained by the Patterns and Practices division of Microsoft prior to becoming an open source platform. Here are the following features we can get for implementing Prism in our Xamarin forms:
Last time in our discussion on creating Azure storage table, using our developer’s account, we have successfully deployed our Azure storage using the M.S. Azure portal. We also used a tool called Azure Storage Explorer in creating our sample Table which also contains sample Entities. For today’s article I will teach you on basic operations, e.g. (Insert, Select, delete) you can perform on your Azure Storage using a C# Console application.
One time I have this application that was already deployed in the production area, the Business owner of the application informed me about the application encountered a system crash when certain operations were performed. I really had a hard time figuring what caused the abnormal termination because I didn’t implement a logging function. To make the story short, I learned my lesson that for every application developed, you should implement a logging function. So in today’s article I want to show you how to implement a NuGet called NLog for you C# applications.
Many of us programmers have the mentality that it’s just okay to implement codes in anyway as long as it is running. Well to tell you the truth you should already change or move away from that kind of mindset. Software development has its own guidelines like abstraction, refinement, modularity and other same concepts that you can use to guide you during coding and avoid the so-called programming pasta. One tool I use in Visual Studio 2015 is Code Metrics. For today I will show you how to generate Code Metrics on your project. Then I plan to discuss deeper on the different code metrics in the next succeeding articles.
In today’s article I will discuss about one of the services provided by Microsoft Azure which is the Azure Table Storage. Now a days we are hearing more on NoSQL (Non SQL, Non Relational, Not Only SQL) which is being adapted by some big companies like Facebook, Google and Amazon because of it’s straight forward usage, high scalability, low latency and high performance. Later on this article we will try to create an Azure Storage table using the M.S. Azure portal then will create afterwards a sample table with sample fields using the Azure Storage Explorer.