Catálogo de publicaciones - libros

As discussed in Chapter 4, the data portal implements a channel adapter pattern, allowing you to select between four technologies for communicating with the server-side data portal components:

It is also possible to create your own custom network channel by implementing Data Portal Client. I Data Portal Proxy on the client, and Server. I Data Portal Server on the server, just as was done in Chapter 4 to create the four proxy/host combinations listed previously.

In this chapter, you’ve seen how to configure an application server to host each of the three remote channels: remoting, Web Services, and Enterprise Services. And you’ve seen how to configure client applications to use those hosts.

Whether you use a remote data portal or not, the framework and concepts discussed in this book should enable you to create applications using object-oriented design concepts while leveraging the power of .NET. Your objects will support data binding in Windows Forms and Web Forms, along with support for encapsulation of validation and authorization logic, in a clear and concise manner.

I’ve thoroughly enjoyed exploring these concepts with you, and wish you the best as you develop your software.

Code well, have fun!

This chapter has discussed the creation of a basic Web Forms UI based on the business objects from Chapter 8. As with the Windows Forms technology in Chapter 9, there are many ways to create a Web Forms interface, and the one I’ve created here is just one option among many.

The key is that the business objects automatically enforce all business rules and provide business processing so that the UI doesn’t need to include any of that code. As you can see, it is very possible to create two very different user interfaces based on exactly the same set of business objects, data access code, and database design.

As shown here, the website is configured for optimal performance, running the Session and the data portal in the same process as the web forms. You could increase scalability and fault tolerance by moving Session into its own process, or onto a state server. You could potentially increase security by running the data portal server components on a separate application server. In either case, all you need to do is change some settings in Web.config; the UI code and business objects will work in all these scenarios.

In Chapter 11, I’ll show how you can create another type of interface to the business objects by using Web Services. Then Chapter 12 will show how to create remote data portal hosts for remoting, Enterprise Services, and Web Services.

This chapter has applied the concepts from Chapter 1 to implement about a third of the framework discussed in Chapter 2. At this point, the framework provides enough functionality for a business developer to build object-oriented systems that support useful concepts such as the following:

Chapters 4 and 5 will finish the business framework. Chapter 4 will focus on implementing the data portal concept and supporting object persistence. Then Chapter 5 will wrap up by implementing a variety of functionality to support a business developer in building an application using mobile objects.

From Chapter 6 on, the focus will be on designing and building a simple business application that illustrates how the classes in the framework can be used to build applications based on mobile business objects.

As discussed in Chapter 4, the data portal implements a channel adapter pattern, allowing you to select between four technologies for communicating with the server-side data portal components:

It is also possible to create your own custom network channel by implementing Data Portal Client. I Data Portal Proxy on the client, and Server. I Data Portal Server on the server, just as was done in Chapter 4 to create the four proxy/host combinations listed previously.

In this chapter, you’ve seen how to configure an application server to host each of the three remote channels: remoting, Web Services, and Enterprise Services. And you’ve seen how to configure client applications to use those hosts.

Whether you use a remote data portal or not, the framework and concepts discussed in this book should enable you to create applications using object-oriented design concepts while leveraging the power of .NET. Your objects will support data binding in Windows Forms and Web Forms, along with support for encapsulation of validation and authorization logic, in a clear and concise manner.

I’ve thoroughly enjoyed exploring these concepts with you, and wish you the best as you develop your software.

Code well, have fun!

This chapter concludes creation of the CSLA .NET framework. Over the past three chapters, you have learned how to support a wide variety of functionality to support the development of business objects. This chapter combined a wide range of capabilities, including the following:

Combined with the support for editable and read-only business objects from Chapter 3, and the data access and mobile object support from Chapter 4, these capabilities make it relatively easy to build a powerful object-oriented business layer for an application.

The remainder of the book will focus on how to use this framework to create business objects, as well as a variety of UIs for those objects, including Windows Forms, Web Forms, and Web Services.

This chapter has applied the concepts from Chapter 1 to implement about a third of the framework discussed in Chapter 2. At this point, the framework provides enough functionality for a business developer to build object-oriented systems that support useful concepts such as the following:

Chapters 4 and 5 will finish the business framework. Chapter 4 will focus on implementing the data portal concept and supporting object persistence. Then Chapter 5 will wrap up by implementing a variety of functionality to support a business developer in building an application using mobile objects.

From Chapter 6 on, the focus will be on designing and building a simple business application that illustrates how the classes in the framework can be used to build applications based on mobile business objects.

This chapter has discussed the basic concepts and requirements for all business classes based on CSLA .NET. I discussed the life cycle of business objects, and walked through the creation, retrieval, update, and delete processes.

The basic structure of each type of business class was covered. There are common requirements, including making all the classes serializable, implementing a common set of code regions for clarity of code, including a Private constructor, and having a nested Criteria class. There are also specific structures or templates for each type of business object, including the following:

Chapter 8 will implement the sample project tracker application classes based on these concepts and templates.

This chapter implemented the business objects designed in Chapter 6, using the templates and concepts discussed in Chapter 7. The result is Project Tracker. Library, the business layer for the sample ProjectTracker application, including the following:

The library also includes classes to support custom authentication:

This business library will be used to create Windows Forms, Web Forms, and Web Services interfaces in the next three chapters.

This chapter has applied the concepts from Chapter 1 to implement about a third of the framework discussed in Chapter 2. At this point, the framework provides enough functionality for a business developer to build object-oriented systems that support useful concepts such as the following:

Chapters 4 and 5 will finish the business framework. Chapter 4 will focus on implementing the data portal concept and supporting object persistence. Then Chapter 5 will wrap up by implementing a variety of functionality to support a business developer in building an application using mobile objects.

From Chapter 6 on, the focus will be on designing and building a simple business application that illustrates how the classes in the framework can be used to build applications based on mobile business objects.

This chapter has discussed the creation of a basic Web Forms UI based on the business objects from Chapter 8. As with the Windows Forms technology in Chapter 9, there are many ways to create a Web Forms interface, and the one I’ve created here is just one option among many.

The key is that the business objects automatically enforce all business rules and provide business processing so that the UI doesn’t need to include any of that code. As you can see, it is very possible to create two very different user interfaces based on exactly the same set of business objects, data access code, and database design.

As shown here, the website is configured for optimal performance, running the Session and the data portal in the same process as the web forms. You could increase scalability and fault tolerance by moving Session into its own process, or onto a state server. You could potentially increase security by running the data portal server components on a separate application server. In either case, all you need to do is change some settings in Web.config; the UI code and business objects will work in all these scenarios.

In Chapter 11, I’ll show how you can create another type of interface to the business objects by using Web Services. Then Chapter 12 will show how to create remote data portal hosts for remoting, Enterprise Services, and Web Services.