Home Library Learn Downloads Support Community
Sign in | United States - English | |
21 out of 39 rated this helpful Rate this topic

FileSystemObject Object

Windows Scripting 5.8

Provides access to a computer's file system.

The following code illustrates how the FileSystemObject is used to return a TextStream object that can be read from or written to.

Code

JScript
Copy 
// JScript
var fso = new ActiveXObject("Scripting.FileSystemObject");
var a = fso.CreateTextFile("c:\\testfile.txt", true);
a.WriteLine("This is a test.");
a.Close();

Code

VB
Copy 
' VBScript
Dim fso, MyFile
Set fso = CreateObject("Scripting.FileSystemObject")
Set MyFile = fso.CreateTextFile("c:\testfile.txt", True)
MyFile.WriteLine("This is a test.")
MyFile.Close

In the example code, the ActiveXObject object is assigned to the FileSystemObject (fso). The CreateTextFile method then creates the file as a TextStream object (a), and the WriteLine method writes a line of text to the created text file. The Close method flushes the buffer and closes the file.

Did you find this helpful?
(2000 characters remaining)
Community Content Add
Annotations FAQ
No Version-Independent Prog ID

The FileSystemObject class does not have a Version-Independent Prog ID, at least under Microsoft Windows XP. 
In particular, the following query returns nothing: 

SELECT COMPONENTID FROM WIN32_CLASSICCOMCLASSSETTING WHERE VERSIONINDEPENDENTPROGID='Scripting.FileSystemObject'

This is against the rules for COM Registry Keys[1]:

Applications must register a version-independent programmatic identifier under the VersionIndependentProgID key.

[1] http://msdn.microsoft.com/pl-pl/library/ms678477(en-us,VS.85).aspx
[2]Hello

History