Conclusion

In this chapter, we've examined some of the key design goals for the business framework ” CSLA .NET ”that we'll build in Chapters 4 and 5. These include the following:

  • n-Level undo capability

  • Tracking broken business rules to tell if our object is valid

  • Tracking whether our object's data has changed (whether or not it's "dirty")

  • Support for strongly typed collections of child objects

  • Providing a simple and abstract model for the UI developer

  • Full support for data binding in both Windows and Web Forms

  • Saving our objects to a database and getting them back again

  • Table-driven security

  • Other miscellaneous features

  • Interchangeability with the one from Expert One-on-One Visual Basic .NET Business Objects

We've also walked through the design of the framework itself, providing a high- level glimpse into the purpose and rationale behind each of the classes that will make it up. With each class, we discussed how it relates back to our key goals to provide the features and capabilities we're looking for in the framework.

Finally, we wrapped up the chapter by organizing our classes into namespaces so that they're easily understood and used, and we determined how to group them into components or assemblies to avoid circular dependencies and to enable the physical deployment scenarios we're after.

In Chapter 4, we'll implement much of the framework, and then in Chapter 5, we'll implement the rest. From there, we'll walk through the implementation of a sample application using the framework, during which process we'll explore more fully how the framework functions and meets the goals we set forth in this chapter. Before then, in Chapter 3, we'll take a quick tour of some of the .NET technologies with which you may not be entirely familiar.



Expert C# Business Objects
Expert C# 2008 Business Objects
ISBN: 1430210192
EAN: 2147483647
Year: 2006
Pages: 111

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net