.NET news » Search results
Search results for query "object mapping" (20):
A multi-level C# 4.0 dynamic object
Importing data with SSIS Object model
Overcome the Barriers Around Using the Custom Class in ASP.NET
In .NET Web applications you can find that in many places custom classes and collections are better choices than the DataSet or DataTable. The custom classes or the custom class collections, which are truly object oriented, allow developers to employ all object-oriented programming techniques.
Unfortunately, .NET Framework and Visual Studio 2005 don’t provide good support of the custom class. As a result, developers often encounter the following three barriers around using the custom class.
DataSet and DataTable are Microsoft’s solutions to these problems. Microsoft provides lots of built-in support of DataSet and DataTable in their development tools and in the .NET Framework library. But the DataSet and DataTable are far from object-oriented. Besides, they have lots of overhead.
Take a Leap Forward with ADO.NET vNext (Part 1)
db4o
ADO.NET Entity Framework Overview
ADO.NET in the next release of Visual Studio code-named "Orcas" features the new Entity Framework. It allows developers to focus on data through an object model instead of through a logical/relational data model. The Entity Framework helps abstract the logical data schema into a conceptual model and allows for multiple ways to interact with the conceptual model through Object Services and a new data provider called EntityClient. This month’s column discusses what the Entity Framework is, how it fits into an application, and how it can be designed and programmed against.
RTextPrinter for .NET
Nested Property Binding
I'm currently in the process of developing an object relation mapper for use with Microsoft SQL server. During this process I've been faced with a number of challenges related to the fact that I will be working with objects rather than datatables. If you've ever tried binding a datagrid to a list of objects, I'm sure you have come across the problem where you wanted to display properties that is not part of the object type itself.
This is normally referred to as nested property binding. Many people create special view objects when this becomes a necessity. I wanted a smoother solution and I wanted it design time. The component I've created derives from Bindingsource and is called ObjectBindingSource. As the name implies the components is designed to be working with objects and not datasets/datatables..


Syndicate