Re: Removing datasets from our architecture...



I would suggest this route:

A. Do it. Custom Business Objects and Custom Collections are alot more
maintainable than DataSets.
B. Pick one entity you would like to change. And convert it ...manually in
your code.
C. After you get a feel for it, then consider using CodeSmith templates.
You may have to create your own template.

The existing CodeSmith templates might be overkill for what you are wanting.
Or rather, after you get the result code, you may be overwhelmed at first.
Its better to get a feeling for Custom Business Objects and Collections
before making that jump.

(on c above) you can create your own template to match your needs. My
company has a code generation template, that maps out our namespaces from
the getgo.
Aka, we can copy and paste the code exactly to our liking because we figured
out how to make the template.


The one place I still use (strong) datasets is reporting. It not worth the
drama (to me) of using Custom Business objects for just reporting needs.


Look at this blog entry:
http://sholliday.spaces.live.com/Blog/cns!A68482B9628A842A!139.entry

and you can also find the 2.0 version as well, but start with the 1.1
version.

There is a MS article I reference as well ("bird's eye view") you should
read. It discusses alot of the different options.

DataSets are good for RAPID development , but for maintainable code that
needs to grow/extend, custom object and collections are worth the effort.

.....

At some point you'll have to make the jump. Consider Unit Tests where you
can compare the old versus new code as well.

When you make the jump, don't try to put in new features at the same time.
Try to keep it the same, get comfortable with the switch, and then integrate
new features.

This is one opinion of many as well.



"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