In Windows Forms MDI applications...

I'm wondering if it is standard practice to create DAL and business objects
as static classes. The only alternative (please enlighten me if I'm wrong
about this) is to instantiate the DAL and business objects in a Form class -
most likely the MDI parent - and then expose the business objects as public
members.

What is standard practice here? [assuming we're not using DCOM or Remoting
or Web services or any other such remote procedure calls].

Thanks!

Your DAL, business objects and other related objects belong in their
own respective libraries. They should not be a part of the WinForm
project. This will provide you flexibility, a layer of abstraction and
cleaner, more logical code.

David Barkol
www.neudesic.com

In addition to all the benefits David mentioned, it also makes it somewhat
easier to reuse code since you can just include those libraries in future
application that need any need similar information already in your DAL
libraries.

Show quoteHide quote

Browse for folders dialog
Why can't you inherit System.Windows.Forms.Form?
Closing form causes validation
Creating a modal process
hierarchical grid
Explorer style interface
Winform rants...
scrolling text
Databinding Textbox on TabPage
DataGridview combobox column