"Expert C# Business Objects" is a good place to start reading, and a
handy investment.
Our implementation using the new System.Windows. Forms.BindingSo urce as
the base class for our business object. I believe you must be using
..Net 2.0 to take advantage of this.
Now our business object can be used as a datasource for any data bound
control, and we can put our business logic into the class. For example,
our business object has an Update() method that validates the data, then
calls writes the changed data back to the database. If validation
fails, the record is flagged in error. A detail form with an error
provider on it can then display the appropriate error message.
It isn't really possible to send you code examples because 1) I'm not
sending out proprietary code ad 2) It would take quite a while to put
together an example for you.
If you still aren't sure how to proceed, you might consider contracting
a local consultant for a couple hours just to get you started. That's
what I did, and it was money very well spent.
Gary
ja*****@gmail.c om wrote:
Hi
Is there a way to seperate code of interface in windows applications
for various design purposes? Just like it can be done in ASP.NET, one
code can be inherited in different skins with different design.
Sincerely
Del