Catálogo de publicaciones - libros
Pro .NET 2.0 XML
Bipin Joshi
Resumen/Descripción – provisto por la editorial
No disponible.
Palabras clave – provistas por la editorial
Software Engineering/Programming and Operating Systems
Disponibilidad
| Institución detectada | Año de publicación | Navegá | Descargá | Solicitá |
|---|---|---|---|---|
| No detectada | 2007 | SpringerLink |
Información
Tipo de recurso:
libros
ISBN impreso
978-1-59059-825-2
ISBN electrónico
978-1-4302-0198-4
Editor responsable
Springer Nature
País de edición
Reino Unido
Fecha de publicación
2007
Información sobre derechos de publicación
© Apress 2007
Cobertura temática
Tabla de contenidos
Use of XML in the .NET Framework
U p until now, you have learned how to work with your own XML data. This includes reading, writing, validating, serializing, and querying XML data. However, Microsoft has used XML extensively in the .NET Framework. The most significant area where XML is used extensively is in application configuration. Further, ASP.NET makes heavy use of XML for representing server controls and data binding. Understanding the use of XML in the .NET Framework is therefore essential for any .NET developer. This chapter introduces you to many of these features. Specifically, you will learn about the following topics: • Remoting • How XML is used in a remoting configuration • ASP.NET server controls • Use of XML in representation of server controls • The XML data source control • Navigational controls of ASP.NET such as TreeView, Menu, and SiteMap • The XML server control • Website configuration files and XML
Pp. 343-412
Creating Services by Using Windows Communication Foundation
C hapter 9 introduced you to web services, and Chapter 11 introduced you to remoting—both of which allow you to develop distributed applications. Web services are mainly used when you wish to communicate across the Internet, whereas remoting is preferred in intranet scenarios. However, in most real-world cases, you need to decide between web services and remoting well in advance because your choice affects your development process. For example, if you decide to use web services, their proxies and XML serialization come into the picture, whereas if you decide to use remoting, activation type and binary serialization come into the picture. At times these differences can prove to be painful. Imagine, for example, that you begin the development with remoting in mind and the application is developed and deployed in a production environment. After a few months, you want to replace remoting components with web services. Can you do that without changing anything in the client application? In most cases, the answer will be a resounding no.
Pp. 413-431