Book Image

Hands-On Mobile Development with .NET Core

By : Can Bilgin
Book Image

Hands-On Mobile Development with .NET Core

By: Can Bilgin

Overview of this book

.NET Core is the general umbrella term used for Microsoft’s cross-platform toolset. Xamarin, used for developing mobile applications, is one of the app model implementations for .NET Core infrastructure. In this book, you'll learn how to design, architect, and develop attractive, maintainable, and robust mobile applications for multiple platforms, including iOS, Android, and UWP, with the toolset provided by Microsoft using Xamarin, .NET Core, and Azure Cloud Services. This book will take you through various phases of application development using Xamarin, from environment setup, design, and architecture to publishing, with the help of real-world scenarios. Throughout the book, you'll learn how to develop mobile apps using Xamarin, Xamarin.Forms, and .NET Standard. You'll even be able to implement a web-based backend composed of microservices with .NET Core using various Azure services including, but not limited to, Azure App Services, Azure Active Directory, Notification Hub, Logic Apps, Azure Functions, and Cognitive Services. The book then guides you in creating data stores using popular database technologies such as Cosmos DB, SQL, and Realm. Finally, you will be able to set up an efficient and maintainable development pipeline to manage the application life cycle using Visual Studio App Center and Visual Studio Services.
Table of Contents (26 chapters)
Title Page
Copyright and Credits
About Packt
Contributors
Preface
Index

The QA process


In each phase of a CD process, the quality of the features should be verified preferably with an automated process or, at the very least, with proper code reviews. This is where the pull request creation and validation process becomes even more important. Nevertheless, as mentioned, the QA of an artifact or a branch is not limited to the CI phases of the process, but runs throughout the CI/CD pipeline.

 

Code review

A healthy development team should be driven by collaboration. In this context, the concept of peer review is extremely important, since it gives the chance for the development team to suggest and advice improvements of a colleague's work. Azure DevOps have two branch policies that directly encourage or even enforce the peer review process. One of these policies is the minimum number of reviewers, and the second one is the automatic code reviewer policy:

Using the Automatic Code Reviewer policy, multiple optional and/or mandatory reviewers can be automatically added...