First of all I want to thank you Rocky for your well written books. I first read your work in 2000 when I read "Professional Visual Basic 6 Business Objects" - in fact that was my first exposure to creating practical, OO code in VB.
Over the past 9 years I have largely been involved in either developing small, procedural apps or working on other peoples' designs and had little say in architectural decisions. In many cases the business needs were so immediate that we simply had to get the code written and working and little thought was given to architecture. Now, I find myself in a position where I am a major contributor to architecure and design decisions in a project to design and develop an entire OO, n-tier web-based system. The first thing I did was to buy and start reading "Expert VB 2005 Business Objects". Since I learned OO coding from reading your books, the CSLA approach seems very natural and easy to me, but there is an unofficial policy in place here to go with SOA. This project is on a very tight timeline and is limited in scope so SOA is not REQUIRED, but I have been told that I SHOULD design the sysytem so it can easily be used by other SOA systems. Part of this is a requirement that EVERY business object must have an interface defined. In fact - it has been strongly recommended that ALL coding use interfaces (ie: UI code to instantiate a business object actually instantiates the Interface rather than the object itself: Dim Ent as IEntity = New Entity())
I have downloaded the CSLA.NET framework and browsed through it. It is rather complex but I can see how powerful and useful it can be. How can I reconcile the framework with the above mentioned requirements? Would I be better off to NOT use the framework but develop my own simplified framework using the same principles? There is much in the framework that will not be required by this project such as n-level undo and such. I still have not finished reading the book - I'm only on Chapter 2 - so if the answers to these questions are in there just point me in the right direction.
Chapter 11 talks about building and consuming services using CSLA.
And if you are using WCF, then the Using CSLA .NET 3.0 ebook has a chapter with great information on using CSLA with WCF services (and on some aspects of WCF services in general).
Thank you. I skipped ahead and scanned chapter 11.
We are not using WCF in this project but I do plan on reading that ebook regardless.
Copyright (c) Marimer LLC