Summary

This chapter presented two approaches to automated deployment. The application launcher design is a "common-sense" solution: It doesn't involve a new .NET redesign, and it works well with disconnected clients that require only periodic updates. For most distributed systems, the application launcher is the best solution.

The application browser is a more ambitious approach that breaks down an entire application into distinct components. It takes more time to develop and test and introduces new issues such as code access security. If you need to create an extremely configurable and automatically updatable application, however, it might be exactly what you need.

Keep in mind that you don't necessarily need these approaches if you just want to create a fixed client application that downloads dynamic (and frequently changing) data from a Web server. The case study in Chapter 17 presents an example with a dynamic client that periodically retrieves a product catalog, stores it locally in XML, and uses the information to tailor its interface accordingly.



Microsoft. NET Distributed Applications(c) Integrating XML Web Services and. NET Remoting
MicrosoftВ® .NET Distributed Applications: Integrating XML Web Services and .NET Remoting (Pro-Developer)
ISBN: 0735619336
EAN: 2147483647
Year: 2005
Pages: 174

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