C# Developeramp;#039;s Guide to ASP.NET, XML, and ADO.NET [Electronic resources] نسخه متنی

اینجــــا یک کتابخانه دیجیتالی است

با بیش از 100000 منبع الکترونیکی رایگان به زبان فارسی ، عربی و انگلیسی

C# Developeramp;#039;s Guide to ASP.NET, XML, and ADO.NET [Electronic resources] - نسخه متنی

Jeffrey P. McManus; Chris Kinsman

| نمايش فراداده ، افزودن یک نقد و بررسی
افزودن به کتابخانه شخصی
ارسال به دوستان
جستجو در متن کتاب
بیشتر
تنظیمات قلم

فونت

اندازه قلم

+ - پیش فرض

حالت نمایش

روز نیمروز شب
جستجو در لغت نامه
بیشتر
لیست موضوعات
توضیحات
افزودن یادداشت جدید








Why a New Object Library for Data Access?


A database application programming interface (API) is a software library that programmers use to perform useful work with a database. Prior to Microsoft.NET, many Web developers on the Microsoft platform used a database API called ActiveX Data Objects (ADO), a COM library that enabled access to data sources.

A notoriously cranky lot, database programmers tend to be irked when the database access API they use is changed. This is because so much depends on the database layer operating correctly and efficiently. The situation is exacerbated when the current database API works well and the new API doesn't provide many compelling benefits.

The version of ADO used by application developers prior to Microsoft.NET worked well for building client/server and traditional Web applications. But the world of application development continues to evolve, and this evolution demands that the tools we use evolve with it. For example, you can manipulate a resultset in the absence of a dedicated database connection in both ADO.old and ADO.NET. In contrast, only ADO.NET provides support for a new type of resultset object (the DataSet), which is relatively easy to create, always disconnected, universally available across any data provider, and powerful.


/ 106