is there a best way? is it really up to the developer on how to code the
app?
Yes, and yes.
There is always a best way (we usually only approach it), but the best way
in one situation may not be the best way in another. That is, there are many
best ways to do many things, but only one best way to do one thing. So, it's
up to the developer to determine the best methodology to use according to
the requirements of the app, and the resources available.
Typed DataSets are quite helpful and can help in terms of productivity, and
even performance, when used in the right situations. They are useful when,
for example, a large set of data may need to be worked with at one time, as
the data can be fetched and cached at one time, and updated separately at
another. On the other hand, if only small portions of a large data store are
being used at any given time, and only for short periods at a time, it may
be better to make the database calls without the cache.
--
HTH,
Kevin Spencer
Microsoft MVP
Chicken Salad Surgery
Orange you bland I stopped splaying bananas?
"CSharpguy" <CS*******@discussions.microsoft.comwrote in message
news:49**********************************@microsof t.com...
I've been reading some articles on 'application architecture' and some
have
say use Typed DataSets in .NET 05 and some use a datalayer class and a
business layer class. Currently I have a class library in 05 were I'm not
using typed datasets, I have a business layer class and my datalayer
classes.
I've been doing some work with typed datasets on a small project but not
using my class library. So my question is, what is the best way and the
recommended way for the 05 architecture?
is there a best way? is it really up to the developer on how to code the
app?
thanks for any suggestions
