Applied XML Programming for Microsoft .NET.pdf - Csbdu.in

persistence, resort to the DiffGram XML format. DiffGrams are the subject of Chapter10.In this chapter, we also examined how ADO.NET objects integrate with the standard.NET Framework run-time serialization mechanism. DataSet and DataTable objectsalways expose themselves to data formatters as XML DiffGrams, thus resulting inlarger output files. We looked at a technique for reducing the size of the serialized dataas much as 500 percent.In ADO.NET, the deserialization process is tightly coupled with the inference engine,which basically attempts to algorithmically extract the layout of the XML stream. Whenloading XML into a DataSet object, the inference engine is involved more frequentlythan not. Because it is not a lightweight piece of code, you should always opt for a clearand effective reading mode and use the inference engine only when absolutelynecessary.As mentioned, in the next chapter we'll tackle a very special XML serialization format—the DiffGram. Among other things, the DiffGram format is the format used to deliverDataSet objects to other platforms through Web services. It is also ideal for setting upintermittent applications—that is, applications that can work both connected to anddisconnected from the system.Further ReadingObject serialization and ADO.NET are the key topics of this chapter. You'll find a lot ofbooks out there covering ADO.NET from various perspectives. I recommend MicrosoftADO.NET, Core Reference, by David Sceppa (Microsoft Press, 2002).It's more difficult to locate a book that provides thorough coverage of objectserialization. Chapter 11 in Programming Microsoft Visual Basic .NET, Core Reference,by Francesco Balena (Microsoft Press, 2002), is an excellent and self-containedreference. If you want a shorter but complete overview, have a look at the followingonline article: http://msdn.microsoft.com/library/enus/dnadvnet/html/vbnet09252001.asp.360