Catálogo de publicaciones - libros

In this chapter, we introduced the smart client and SOSC. First, we described the evolution of the smart client, in the context of the evolution of client architecture: from stand-alone applications, to thick clients in client/server applications, to thin clients in web-based applications, and to the new smart client architecture. Then we explored thick and thin clients in more detail, because smart clients are designed to have the advantages of both of these types of clients, while avoiding their disadvantages. Finally, we looked at the makeup of smart clients and SOSCs, which are the subject of this book.

In the next chapter, you’ll learn about the various types of smart clients.

In this chapter, we discussed some of the issues in supporting offline functionality. We said that the biggest challenge smart client developers face is having to manage two different data stores and synchronizing the two. Moreover, we said that the key to reducing the complexity associated with implementing offline support is to identify what functionality will be supported while offline and the data associated with it, and to do so early in the design of the application as presented in the section “Identifying Locally Storable Data.”

We also discussed the Offline Application Block and the Caching Application Blocks, which are reusable blocks that can help you to implement offline facilities with your own smart client applications. Next, we covered ways to maintain data consistency. We concluded with an introduction to managing sensitive data.

In the next chapter, we’ll move on to the topic of deployment and explain the various techniques available for deploying and updating smart clients.

In this chapter, we discussed two reference implementations of WinForms smart clients. We thoroughly dissected the TaskVision solution, and then highlighted the important aspects of IssueVision. Using these two implementations as guides, you can begin to build your own smart clients.

In the next two chapters, we’ll cover Office smart clients and mobile smart clients. After that, we will talk in depth about deployment techniques and technologies specific to WinForms smart clients.

In this chapter, we discussed the two types of Office smart clients: VSTO-based Office smart clients and IBF-based Office smart clients. Both of these smart clients leverage the power of Visual Studio and Office to enable enterprise smart client applications. VSTO-based smart clients are best suited for applications whose core functionality is either Word or Excel (at the moment). These types of smart clients present the core Office product user interface with additional functionality on top of the Office product. IBF-based smart clients connect an Office product to LOB systems. This type of smart client is best suited for organizations that have a large number of employees who spend most of their workday using one (or more) Office product.

Up to this point, we have discussed WinForms and Office smart clients. In the next chapter, we’ll discuss mobile smart clients.

In this chapter, we introduced the Windows mobile platform for smart device development, including the .NET CF. Then we looked at the tools for developing smart device applications in Visual Studio. As an example, we dissected the Pocket PC version of the FotoVision smart client application.

We also discussed deploying smart device applications, including the OTA, MSI, and sneakernet approaches. Often, you need to use a variety of deployment approaches. For example, you may need to use sneakernet for the initial deployment, and then use OTA for updates. Finally, we introduced some of the up-and-coming features in Visual Studio 2005.

In the next chapter, we’ll discuss a feature that is common to all of the various types of smart clients: offline support.

In this chapter, we discussed some of the issues in supporting offline functionality. We said that the biggest challenge smart client developers face is having to manage two different data stores and synchronizing the two. Moreover, we said that the key to reducing the complexity associated with implementing offline support is to identify what functionality will be supported while offline and the data associated with it, and to do so early in the design of the application as presented in the section “Identifying Locally Storable Data.”

We also discussed the Offline Application Block and the Caching Application Blocks, which are reusable blocks that can help you to implement offline facilities with your own smart client applications. Next, we covered ways to maintain data consistency. We concluded with an introduction to managing sensitive data.

In the next chapter, we’ll move on to the topic of deployment and explain the various techniques available for deploying and updating smart clients.

In this chapter, we discussed various approaches to deploying WinForms smart clients. We covered NTD, OTD, and MSI installer deployment. Then we focused on the next-generation deployment solution called ClickOnce.

You learned that the ClickOnce technology builds on the previous attempts to solve the problems associated with deploying rich clients. We showed examples of deploying and updating smart clients with ClickOnce, and then demonstrated how you can use the ClickOnce API to handle deployment tasks programmatically.

Finally, we discussed the Application Updater component and the UAB. These technologies are useful for cases where you can’t use ClickOnce deployment.

In the next chapter, we will introduce XML Web Services and how smart clients can use them.

This chapter provided an overview of XML Web Services. We began with a review of two business cases that demonstrated how using XML Web Services and smart clients can lower future development costs and give applications a broader reach. Next, we summarized the benefits and drawbacks to using an associated technology with XML Web Services. Then we reviewed each of the technologies used by XML Web Services: XML, SOAP, WSDL, UDDI, and DISCO. Finally, we went through the steps to develop an XML Web Service with Visual Studio .NET 2003 or 2005.

In the next chapter, we will explain how integrating these elements into a service-oriented architecture will enhance your smart client application.

In this chapter, we discussed some of the issues in supporting offline functionality. We said that the biggest challenge smart client developers face is having to manage two different data stores and synchronizing the two. Moreover, we said that the key to reducing the complexity associated with implementing offline support is to identify what functionality will be supported while offline and the data associated with it, and to do so early in the design of the application as presented in the section “Identifying Locally Storable Data.”

We also discussed the Offline Application Block and the Caching Application Blocks, which are reusable blocks that can help you to implement offline facilities with your own smart client applications. Next, we covered ways to maintain data consistency. We concluded with an introduction to managing sensitive data.

In the next chapter, we’ll move on to the topic of deployment and explain the various techniques available for deploying and updating smart clients.

In this chapter, we described how to develop an SOSC by combining the SOA and service client technologies. You learned how adding a smart agent, a special component of an SOSC, can enhance media and communication agility for a smart client. We then discussed how to maintain state and use concurrency within this environment. We concluded by returning to the example developed in the previous two chapters to show how XML Web Services and an SOA can be leveraged by a smart client. The example demonstrated how SOSCs can reduce the duplication of clients and provide a seamless solution that allows users to reach both local and global resources. In the next chapter, we will discuss some of the difficulties in testing an SOSC in this environment.