we are currently beginning on the path of .NET, previously we have built N-Tier applications using the method of mapping database tables each to a single object and a collection object. By using these objects we built the UI either in VB 6 or ASP.
All our objects are programmed in VB6 as ActiveX dll projects.
Our single object would provide functions to load, save, delete etc a single record from a table, it would also have properties that matched to fields in the table. Our collection objects would retreive a collection of single objects using functions.
We never used databinding on the front-ends, basically all the validation and manipulation of data was done through the objects, and it used recordsets, commands etc to do data updates etc.
I hope I have made myself clear.
Now here is the question, from looking at VB.NET, I am now wondering if this is the right way for developing new applications in .NET. I am sure we will not use a lot of the new power of ADO.NET and VB.NET, if we don't use databinding controls such as the datagrid.
See my previous experience in old VB was not to touch databinding, as you lost a lot of control especially when validating data.
What are people doing in the real working world with .NET, having objects return datasets and using them? Or building them in wrappers?
Any thoughts and opinions, would be appreciated.