Reflection or Strongly Typed data sets
Posted on 2004-08-01
I've been using reflection for some time now to easily translate database schema's to c# objects. Basically my reflection updates/Inserts/ deletes itself from a database. I also have an init function that uses a stored procedure to get it's own data from the database.
The beauty of this thing is that when I add a column to a table all I have to do is update the stored procedures that I'm using and add a property in the object. I don't have to manually create and fill out more properties.
I'm wondering if I should move to strongly typed data sets or not? I've tried to read up on it but I'm still a little unsure as to how they work and the pros and cons of em.
Please some information on this subject would be most helpful.
I'm looking for a solution that is flexible enough to handle changes to the underlying schema and is easy to maintain.