The business objects are a package of data and code to manipulate that data, and are capable of migrating, via Microsoft's .NET marshalling system, from one machine to another, depending where they logically fit at any stage in the process's lifetime. The book uses as an example the development of a framework to handle business objects, and anyone using this book will get a fairly good grounding in some key .NET technologies - remoting, Windows forms, and web forms for instance. This, in itself is a useful thing, so why am I doubtful about the overall thrust of the book? I can answer that in one word. Debugging. How do you debug code which moves around different physical and logical machines and operating environments? Significantly, there is no sustained discussion of the issue or development of suitable tools in the book, and to my mind this is a fatal flaw.
'Expert C# Business Objects' by Rockford Lhotka Back to the Phlogiston Blue top page If you have any questions or comments about the articles on my web site, click here to send me email. |