Book Image

.NET Core 2.0 By Example

By : Neha Shrivastava, Rishabh Verma
Book Image

.NET Core 2.0 By Example

By: Neha Shrivastava, Rishabh Verma

Overview of this book

With the rise in the number of tools and technologies available today, developers and architects are always exploring ways to create better and smarter solutions. Before, the differences between target platforms was a major roadblock, but that's not the case now. .NET Core 2.0 By Example will take you on an exciting journey to building better software. This book provides fresh and relevant content to .NET Core 2.0 in a succinct format that’s enjoyable to read. It also delivers concepts, along with the implications, design decisions, and potential pitfalls you might face when targeting Linux and Windows systems, in a logical and simple way. With the .NET framework at its center, the book comprises of five varied projects: a multiplayer Tic-tac-toe game; a real-time chat application, Let'sChat; a chatbot; a microservice-based buying-selling application; and a movie booking application. You will start each chapter with a high-level overview of the content, followed by the above example applications described in detail. By the end of each chapter, you will not only be proficient with the concepts, but you’ll also have created a tangible component in the application. By the end of the book, you will have built five solid projects using all the tools and support provided by the .NET Core 2.0 framework.
Table of Contents (16 chapters)
Title Page
Packt Upsell
Contributors
Preface
Index

Summary


In this chapter, we learned about Entity Framework and Entity Framework Core, and understood the features of each and the differences between the two. We also learned that we should use EF Core only if EF cannot be used or there is a pressing cross-platform requirement to use EF Core. We learned how to do CRUD operations using EF Core by creating a simple app. We then developed a simple movie booking app and learned how to deploy it using Visual Studio. We also saw how we can monitor our web app by enabling Application Insights. So far, we have only seen monolithic apps where all the APIs reside in one web app. If that one web app goes down, our entire app can come to a standstill. There is a way to circumvent this by deploying the app in smaller, independent modules, called microservices. In the next chapter, we will explore microservices.