Re: Removing datasets from our architecture...

Code generators are great, and highly recommended. However, it's not worth ripping out working code unless you have a lot more DB code still needing to be written. You should not make the change merely for the sake of making the change. Only do so if the benefits in time/quality/maintenenance for the remainder of the project outweigh the time & risk of making a major change to functioning code.

--
Andrew Faust
andrew[at]andrewfaust.com
http://www.andrewfaust.com


"John Sheppard" <nospam@xxxxxxxxxxxx> wrote in message news:fh44sp021pi@xxxxxxxxxxxxxxxxxxxx
Hello,

I was curious as to peoples thoughts on using tools such as MyGeneration/CodeSmith to generate business objects as opposed to using datasets? We currently use datasets, for various reasons I *suspect* we want to move away from using them....

I guess my secondary question is will it be a complete rewrite to remove datasets from the application? :( or is there an easy way to do it? (They are HEAVILY used)

I wonder if we will be stuck with them forever more, or should I go through the pain of changing *now*, somewhat early in the development process, (6 months) ...or should I just live with them...

Background Info
MsAccess Backend, Webservice consumed by a WinForms application all in .net

Thank you for any thoughts anyone has...
John

.

Loading