Pretesting UNC and LFN Support

[This is preliminary documentation and subject to change.]

The following sections describe the pretesting for Universal Naming Convention (UNC) paths and long file names (LFNs).

Pretesting direct network browsing with UNC paths

Open a file, and use the Save As command to save the file to a standard server with an LFN and with various UNC paths (for example, \\ServerName\MySubdirectory\MyLongFileName).

It should be possible to save and retrieve files without specifically referring to a network drive letter.

Proper LFN handling

LFN handling must:

• Allow plus signs ( + ), commas ( , ), semicolons ( ; ), equal signs ( = ), and square brackets ( [ ] ) anywhere in the file name.
• Not save leading or trailing spaces. You can test for this by removing the name inserted into the Save As dialog box, pressing the spacebar several times, typing "test", and then pressing the spacebar several more times. Your program should strip the spaces and add an extension, returning the file name "test.ext" (not " test .ext").
• Not save question marks.
• Support 255 characters (including the path and extension).
• Save to a UNC path, such as \\Server\Directory\Filename.
• Add an extension before saving a file. For example, "test" should be saved as "test.ext".

Pretesting 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

Pretesting LFN Handling for Utilities

1. Run the utility (your product), and manipulate several LFN files.
2. Open these files both with their LFNs and with their 8.3 aliases, and make sure both relate to the same file.
3. Check overall LFN file structure to ensure its integrity has not been damaged.