If you don’t want the control to create and destroy instances, you can override the default behaviour, capturing the Creating and Disposing events.If it’s an instance method, it will create an object of the class, it will call the method, and then destroy the instance (there is an exception to this, but more about it later).If it’s a static method, it will get the parameters and call it.Each time the ObjectDataSource needs to make a CRUD operation, it will try to find (using reflection) the method to call (of course, you need to set some properties to help it).This object (from now, the data mapper object) has to be designed with some guidelines in mind, to be used properly by the ObjectDataSource: You specify the type of this object to the ObjectDataSource using the TypeName property. ObjectDataSource needs an object that will take care of the CRUD operations (Create, Retrieve, Update, and Delete) of your domain objects. If you want to improve your knowledge about the new data binding infrastructure, look at the references at the bottom of the article. Knowing how the new data binding infrastructure works helps, but it's not required to understand most of the article. ObjectDataSource lets us integrate our own objects in the data binding framework without much work, but we need to understand how this beast works. With the new data binding infrastructure and the ObjectDataSource, this is easier.
NET Framework, it was difficult to integrate our own domain objects into the presentation layer, and nearly impossible to obtain an integration level like the DataSet.