Ive been lucky enough to be involved in two .net projects so far where I
have been able to implement my own takes on the CSLA in .net. Neither of
these have been ideal solutions - I know how I would go about improving
things if I could start again! Neither has really played to all the
advantages of vb.net over vb 6. 

The first time around I went for a multi-tiered system. I had 3 layers of
object - a set of data centric objects, a set of gui-centric objects, and
then business objects which encapsulated validation etc which effectively
got fired backwards and forwards between the two other layers. This was
unfortunatley proving quite complex to implement and even more difficult to
explain to new people coming into the project. In retrospect I probably
dived in a little deep a little early. 

The second implelemtation is more basic - one set of objects with both
busniess and data centric logic in them. However by this time I had managed
to scrub a lot of vb-6 ways of doing things from my head, and begin to make
proper use of the "new" oo features of vb.net - eg inheritence. This time
around I also built a tool to aid RAD, wich builds my basic classes based
on tables. I know good database design <> good oo design - but I find my
objects correspond with my tables enough to make it worthwhile.

Time pressure and the need to produce results means I havent put as much
time into looking at this as I want to. I was quite hopefull for the WEO
object builder book - and while it gave me some good ideas and helped me
understand .net better, it didnt quite seem to give me the answers I'm
looking for - thats what I am hping for from this book!