Fog Creek Software
Discussion Board

Welcome! and rules

Joel on Software

Business Logic UI - Physical Separation

I'm learning .NET now and trying to figure out which is the best .NET practise for UI - Business Logic Separation.

Any articles? In ideal world business logic objects have to:

1.  Be equally easily accessible from Web and Windows Forms.
2.  Handle DB connections automatically (ideally very easily portable from ADO.NET to ODBC and vice versa).
3.  Contain business rules
4.  Can be easily configurable/portable to make use of existent application servers.
5.  Be as "future proof" as possible.

I realise that I have to use DataSets for most of data operations as they have the best support within the framework.

I'd be grateful for your ideas.

Vlad Gudim
Tuesday, February 17, 2004

DB connections "handling" in my opinion includes connections pool management :-)

Vlad Gudim
Tuesday, February 17, 2004

I'm already reading Best Practices for Using ADO.NET (, but still will be happy for anyone sharing the experience.

Vlad Gudim
Tuesday, February 17, 2004

Expert One-on-One Visual Basic .NET Business Objects
by Rockford Lhotka

This book has made me a wealthy man and it addresses every single one of your needs and then some.

Jason Watts
Tuesday, February 17, 2004

I would second that (well, I'm not rich from it yet, but Rocky's stuff is good). If you don't like VB.NET, he has a C# version coming out later this year.

And no, you don't *have* to use DataSets. If you read the book, you'll discover some alternatives.

Dave Hallett
Wednesday, February 18, 2004

Thanks guys,

I'll try to order this book.

Vlad Gudim
Wednesday, February 18, 2004

*  Recent Topics

*  Fog Creek Home