Export (0) Print
Expand All
This topic has not yet been rated - Rate this topic

File I/O Classes

These classes provide an interface to traditional disk files, in-memory files, Active streams, and Windows sockets. All of the classes derived from CFile can be used with a CArchive object to perform serialization.

Use the following classes, particularly CArchive and CFile, if you write your own input/output processing. Normally you do not need to derive from these classes. If you use the application framework, the default implementations of the Open and Save commands on the File menu will handle file I/O (using class CArchive), as long as you override your document's Serialize function to supply details about how a document serializes its contents. For more information about the file classes and serialization, see the article Files in MFC and the article Serialization.

CFile
Provides a file interface to binary disk files.
CStdioFile
Provides a CFile interface to buffered stream disk files, usually in text mode.
CMemFile
Provides a CFile interface to in-memory files.
CSharedFile
Provides a CFile interface to shared in-memory files.
COleStreamFile
Uses the COM IStream interface to provide CFile access to compound files.
CSocketFile
Provides a CFile interface to a Windows Socket.

Related Classes

CArchive
Cooperates with a CFile object to implement persistent storage for objects through serialization (see CObject::Serialize).
CArchiveException
An archive exception.
CFileException
A file-oriented exception.
CFileDialog
Provides a standard dialog box for opening or saving a file.
CHtmlStream
Handles caching HTML output. Functionally similar to CMemFile.
CRecentFileList
Maintains the most recently used (MRU) file list.

See Also

Class Library Overview

Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft. All rights reserved.