Re: Drag and drop DAL

From: Roger (roger.wallin_at_luukku.com)
Date: 06/17/04 

Date: 17 Jun 2004 02:03:37 -0700

I think DAAB is OK. But you will probably lose some of the graphical
aid that you have got from Visual Studio in the previous technique.

I can't figure out why Visual Studio isn't offering a graphical
abstraction of the typical 3-tier (n-tier) architecture, with
different design "surfaces" for the presentation, business and
data-tier. Such a graphical abstraction would suite 90% of all
business-application forms being developed.
The infrastructure could offer smart presentation and handling of the
search-profiles, passing data through the tiers, generation of
suitable stored procedures etc.

I don't think that this kind of abstraction would destroy the
generality of Visual Studio (or dotnet). Neither would it prevent
people to choose their own programming practices, architecture and
performance improvements.

Perhaps MS just want to offer the platform and ...

    Regards Roger.

"SA" <informatica@freemail.nl> wrote in message news:<OY8ntsXSEHA.4068@TK2MSFTNGP09.phx.gbl>...
> Hi,
>
> I have been using this technique in 3-tier applications for 2 years now. It
> works just fine, is very maintainable, and offers a good standardized
> approach.
>
> I use Typed DataSets as business objects, and of course, there are some
> concerns there from people who prefer a more pure OO based approach. I am
> not one of them ;o)
>
> However, for a much larger scale project I will be starting soon, I will be
> considering the Data Access App Block from MS, which is probably slightly
> different (I am guessing here...)
>
> HTH
>
> --
>
> Sven
>
>
> "Roger" <roger.wallin@luukku.com> wrote in message
> news:64adabd6.0405230636.501ac919@posting.google.com...
> > Some weeks ago I jumped into an article describing how to comply with
> > a good layered architecture, yet still being able to use the wizards
> > and other drag and drop methods that is usually used in the demos
> > describing the data-access directly from the form.
> > The idea was that any class that derives from Component will have a
> > design surface in Visual Studio. The article can be found at:
> > http://www.15seconds.com/Issue/030401.htm
> > I found this DAL surprisingly flexible. Does anyone have any
> > comments(advantages/disadvantages)?
> >
> > Regards Roger.

Relevant Pages

  • Re: MSDN Help not available in Visual Studio
    ... Be very careful who you do business with ... >>> But I am unable to get help from the VB6. ... MSDN Library Unable to Display Help from Within Visual Studio ...
    (microsoft.public.vb.general.discussion)
  • Delphi to Visual Studio Conversion Project
    ... Any comments on the wisdom of a conversion like this? ... Is there really a scaling problem that VS can handle that Delphi can't? ... Service management software from Delphi client/server to Visual Studio .Net based 3-tier architecture. ... This will move all software for the product to a more scalable and flexible 3-tier architecture and on more modern Visual Studio based tools. ...
    (borland.public.delphi.non-technical)
  • Re: eclipse editor
    ... I've used it (Visual Studio ?) and _hated_ it. ... Sourcecode flies around when you move the mouse by accident. ... business. ...
    (comp.lang.java.softwaretools)
  • Add Publisher Name to Published VS2005 Project
    ... I use Visual Studio 2005 to publish software to clients. ... result I need is to simply put our business' name in the dialog box ... b/c the .dll doesn't pass the strong name check. ...
    (microsoft.public.dotnet.security)
  • Re: Web Developer 2005 Express v. VS.NET 2003
    ... Visual Studio is designed for full-tiered solutions. ... ASP.NET application is simply UI, without any business or data ... Testing tools (Enterprise Architect) ... Design tools ...
    (microsoft.public.dotnet.framework.aspnet)