Without knowing the specs of your application, I cannot give you a firm
answer either way.
The drag and drop functionality will fit most read only implementations
without killing the "best practices" scenario (I disagree with my own
statement a bit, but you can always refactor to libraries and setting up
ASP.NET as pure GUI later, if the app grows). For simple edits, etc., it is
also fine. It is when you step outside of the box that you get squashed.
The main reason to go away from this model is either reuse or
maintainability. If you can reuse the business objects across multiple apps,
then the drag and drop, all in one, objects really, really suck. The same is
true if you need to extend the app, as the all in one objects become far
less maintainable.
If you head to a fairly standard business and data tier, consider ORM
products or a custom code gen for your work. This will help you if you need
schema changes and increase maintainability.
My preference is this (depends from project to project, of course);
Web app/Windows app - pure gui (bind, basic bozo validation)
Facade - translates business to GUI
Business - business type validations primarily, but ensure no bozo
validations blow up below this level, as DB blow ups are expensive
DAL - rather generic or generated
Data - this is generally sprocs on top of the DB (physical storage)
The facade is almost always necessary, IMO, esp. if you think you might ever
offer the same functionality to a smart client.
--
Gregory A. Beamer
*************************************************
Think Outside the Box!
*************************************************
"CSharpguy" <CS*******@discussions.microsoft.com> wrote in message
news:28**********************************@microsof t.com...
I'm coding my first business web app in .NET 2.0 and its only a read only
web
app. I'm just pulling data from the database and allowing users to filter
the
data in the grids by using dropdowns. I've been reading and seen how you
can
drag and drop the controls and bind them that way, though I'm used to
coding
using a business layer and datalayer. So my question is since this is only
a
view only site, would it make more sense to use the new 'datasource'
controls
on 05 or keep coding using a business and datalayers?
I want to use the new tools in 05 but, what is the recommended 'best
practice' way?