This pattern is used to create and perform new operations onto a set of objects without changing the object structure or classes. This pattern enables loose coupling and addition of new operations without changing the existing structure.
This pattern is used to define the basic steps of an algorithm and allow the implementation of the individual steps to be changed. This pattern looks similar to the strategy design pattern. The main difference is the ability to change the parts of an algorithm rather than replacing an entire algorithm.
This pattern involves the removal of an algorithm from its host class and putting it in a separate class. As you know, there may be multiple strategies which are applicable for a given problem.
This pattern is used to alter the behavior of an object when it’s internal state changes. In this pattern, an object is created which represent various states and a context object whose behavior varies as its state object changes.
This pattern is allows a single object, known as the subject, to publish changes to its state and other observer objects that depend upon the subject are automatically notified of any changes to the subject's state.
This pattern used to capture the current state of an object and store it in such a manner that it can be restored at a later time without breaking the rules of encapsulation.
This pattern allows multiple objects to communicate with each other’s without knowing each other’s structure. This pattern defines an object which encapsulates how the objects will interact with each other’s and supports easy maintainability of the code by loose coupling.
This pattern is provides a way to access the elements of a collection object in sequential manner without knowing its underlying structure.
This pattern evaluates/ interprets the instructions written in a language grammar or notations. This pattern involves implementing an expression interface which tells to interpret a particular context. This pattern is used in the compilers or parsers or Macro expansions.
Xamarin.iOS is a part of Xamarin family to build native iOS app with C# and Xamarin. Xamarin.iOS offers the same UI controls that are available in objective-C or swift language and Xcode.
Xamarin.Android is a part of Xamarin family to build native Android app with C# and Xamarin. Xamarin.Android provides the same UI controls as you have in Android with Java.
Xamarin is a free open-source framework to build truely native cross-platform mobile apps using C# .NET for iOS, Android or Windows. It runs on Mono and .NET to build apps with native performance and native UI. Xamarin allows you to develop native apps using C# language and platform specfic tools/SDKs and share the same code across multiple platforms like iOS, Android or Windows.
Today's we are living in the age of mobile phones. Every one using mobile phones for various daily activities like chatting, sharing, shopping etc. Mobile apps have changed the way of browsing the web and doing online activities.
In this article you will learn how to use the repository pattern for CRUD operations and how to combine it with unit of work patterns. Before goining to write the code, let's understand repository and unit of work patterns separately.
To get started with TypeScript make sure you have TypeScript Supported IDE. In this article, we will use free, open source and cross platform IDE - Visual Studio Code. Make sure you have installed following software to get started with TypeScript development.