Using File I/O
Desktop Framework developers will be aware that programmatic access to file I/O is found in the System.IO namespace. This is also true of the Compact Framework, where I/O is encapsulated by abstracting the concept of a stream used to read and write data from the “backing store,” or a medium used to store the data. Because of this abstraction, you can think of the System.IO namespace as consisting of three logical components, as shown in Figure 3-1.
Figure 3-1. File I/O. The major classes of the System.IO namespace are broken down into components, including (a) streams, (b) readers and writers, and (c) file system classes.
For eVB ...
Get Building Solutions with the Microsoft .NET Compact Framework: Architecture and Best Practices for Mobile Development now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
