Pretesting UNC and LFN Support

[This is preliminary documentation and subject to change.]

The following sections describe the pretesting for Uniform Naming Convention (UNC) paths and Long File Names (LFNs).

Test direct network browsing with UNC paths

Open a file and then use the Save As command to save the file to a standard server with a Long File Name (LFN) and with various Uniform Naming Convention (UNC) paths (for example, \\ServerName\MySubdirectory\MyLongFileName).

Proper handling of LFNs

Basically, LFN handling must do the following:

Testing proper LFN handling

Test each of the allowed file names in the following list. Note that the pound sign ( # ) in the names below is intended to represent a spacebar space:

test
test#test#test#test
test#1234567890[up to a total of 260 characters]

You should also test the following list of file names, which should be saved to the hard disk as indicated. Again, the pound sign ( # ) in the names below is intended to represent a spacebar space, and ext is intended to stand for the file extension that is appropriate to your application:

test                (should be saved as "test.ext")
###test             (should be saved as "test.ext")
test###             (should be saved as "test.ext")
test#;#+#,#=#[#]    (saved as "test#;#+#,#=#[#].ext")

\\folder#one\folder#two\folder#three\folder#four\file

Testing LFN Handling for Utilities: