Book Image

ASP.NET Core MVC 2.0 Cookbook

By : Jason De Oliveira, Engin Polat, Stephane Belkheraz
Book Image

ASP.NET Core MVC 2.0 Cookbook

By: Jason De Oliveira, Engin Polat, Stephane Belkheraz

Overview of this book

The ASP.NET Core 2.0 Framework has been designed to meet all the needs of today’s web developers. It provides better control, support for test-driven development, and cleaner code. Moreover, it’s lightweight and allows you to run apps on Windows, OSX and Linux, making it the most popular web framework with modern day developers. This book takes a unique approach to web development, using real-world examples to guide you through problems with ASP.NET Core 2.0 web applications. It covers Visual Studio 2017- and ASP.NET Core 2.0-specifc changes and provides general MVC development recipes. It explores setting up .NET Core, Visual Studio 2017, Node.js modules, and NuGet. Next, it shows you how to work with Inversion of Control data pattern and caching. We explore everyday ASP.NET Core MVC 2.0 patterns and go beyond it into troubleshooting. Finally, we lead you through migrating, hosting, and deploying your code. By the end of the book, you’ll not only have explored every aspect of ASP.NET Core MVC 2.0, you’ll also have a reference you can keep coming back to whenever you need to get the job done.
Table of Contents (26 chapters)
Title Page
Copyright and Credits
Packt Upsell
Contributors
Preface
Index

Introduction


In this chapter, we will learn how to access data in other ways different to Entity Framework in ASP.NET Core. We will do that with micro ORMs, such as Dapper and OrmLite (but we could use also Massive, SimpleData, or PetaPoco); with NoSQL Databases, such as MongoDB and ElasticSearch (but we could also use Redis, RavenDB, DocumentDB, and so many others); and with the database capabilities of Azure.

Micro ORMs

A micro ORM is a lightweight and performant ORM.

That does not mean that the other ORMs, such as Entity Framework, NHibernate, and others, cannot be performant, but it does mean they need some configuration (no entity tracking, use of stored procedures). They are faster, and they have fewer features because they don't want to cover all the possible scenarios.

These Micro ORMs will often allow us to map the result of a SQL request to a CLR object directly, as AutoMappers do. However, they will not track the state of our entities, have an object relational representation in memory...