Advertisement

© 2008

Pro LINQ Object Relational Mapping with C# 2008

  • Authors

Benefits

  • One of the first books to satisfy the growing demand for a detailed explanation of how object relational mapping methodologies can be applied through the LINQ data access layer

  • Provides detailed A-Z coverage of the key concepts and ideas in a clear, easy to follow, manner

  • Provides a detailed worked case-study that readers can easily tailor to their own circumstances

Book
  • 4.9k Downloads

Table of contents

  1. Front Matter
    Pages i-xx
  2. Object-Relational Mapping Concepts

  3. LINQ to SQL Examined

    1. Front Matter
      Pages 45-45
    2. Pages 79-110
  4. Entity Framework Examined

  5. The Bank of Pluto Case Study

  6. Building on the Bank of Pluto Foundation

    1. Front Matter
      Pages 309-309
    2. Pages 311-345
  7. Back Matter
    Pages 365-383

About this book

Introduction

It is nearly impossible today to write enterprise software without the use of one or more relational databases. Granted, there are cases when the data is transient and not stored in a database, but for the most part, software needs to consume and manipulate data in a database. It sounds easy, but there are hundreds of ways to connect software systems to databases and thousands of people who think they have the skeleton key for data access layers. Pro LINQ Object Relational Mapping in C# 2008 explains an efficient, repeatable way to apply industry design patterns to build scalable object–oriented data access layers.

Object relational mapping (OR/M) has been a gray area in Microsoft development for many years. It's not that Microsoft language developers don't understand OR/M; in fact, the opposite is true, as is exemplified by the glut of third–party .NET OR/M tools on the market. The struggle has come more from the lack of native tools with the object–oriented and object persistence capacity to effectively work in this arena. With the inception of .NET, Microsoft overcame the first obstacle by developing an object–oriented environment and framework. The second obstacle, the native object persistence layer, is only now being realized with the introduction of Language Integrated Query (LINQ) and LINQ's children, the Language Integrated Query for Relational Databases (LINQ to SQL) and the Language Integrated Query for the ADO.NET Entity Framework (LINQ to Entities). The gray area no longer exists, and the .NET developers of the world finally have the native tools required to build modular, reusable data access layers.

Keywords

.NET ADO ADO.NET Boo C# LINQ SQL Scala relational database

About the authors

Vijay P. Mehta has been working as a software engineer and architect for the last 12 years. Starting off in the VC++/ATL, MFC, Win32, and VB6 worlds, Vijay later moved on to Java and .NET development. With his current focus on C# and .NET, Vijay holds a number of Microsoft certifications and has written a number of articles on .Net and Microsoft-focused development. Working as an architect for a financial services software company in Indianapolis, Vijay spends the bulk of his time designing and implementing large, cutting-edge software systems.

Bibliographic information

Industry Sectors
Pharma
Automotive
Chemical Manufacturing
Biotechnology
IT & Software
Telecommunications
Law
Consumer Packaged Goods
Engineering
Finance, Business & Banking
Electronics
Energy, Utilities & Environment
Aerospace