O'Reilly logo

Building Solutions with the Microsoft .NET Compact Framework: Architecture and Best Practices for Mobile Development by Jon Box, Dan Fox

Stay ahead with the world's most comprehensive technology and business learning platform.

With Safari, you learn the way you learn best. Get unlimited access to videos, live online training, learning paths, books, tutorials, and more.

Start Free Trial

No credit card required

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 ...

With Safari, you learn the way you learn best. Get unlimited access to videos, live online training, learning paths, books, interactive tutorials, and more.

Start Free Trial

No credit card required