MrmIndexFileAutoQualifiers function

Adds a file resource to a Resource Indexer, inferring the resource name and qualifiers from the file path. Note that it is the resource name that is indexed, not the file. In other words, this function does not search the filename (or file contents) looking for things to index.

See File resources in MRM for more info.

Syntax

HRESULT HRESULT MrmIndexFileAutoQualifiers(
  _In_ MrmResourceIndexerHandle indexer,
  _In_ PCWSTR                   filePath
);

Parameters

indexer [in]

Type: MrmResourceIndexerHandle

A handle identifying the resource indexer to add the resource to. This handle is returned via a call to MrmCreateResourceIndexer or one of the related MrmCreateResourceIndexer...* functions.

filePath [in]

Type: PCWSTR

The file path to be added to the index, and from which to infer both the resource name and the qualifiers. See the Remarks section below for more info.

Return value

Type: HRESULT

S_OK if the function succeeded, otherwise some other value. Use the SUCCEEDED or FAILED macros (defined in winerror.h) to determine success or failure.

Note that this function may succeed even if you pass an invalid value for the filePath parameter. The error will be reported as 0x8007000B (HRESULT_FROM_WIN32(ERROR_BAD_FORMAT)) when you try to create the PRI file via MrmCreateResourceFile or one of the related functions. See Remarks for more info.

Remarks

This function is equivalent to MrmIndexFile except the resourceUri and qualifiers parameters are inferred from the filePath argument. Given a filePath of the form path1\path2\pathn\filename, the following basic algorithm is used:

1. Let resourceName be the string ms-resource:///Files/.
2. Let qualifiers be an empty string.
3. For each path segment in filePath, check if it consists of a valid qualifier list string (see Qualifiers in MRM for more info). If so, append those qualifiers to qualifiers, otherwise append it to resourceName.
4. For filename, split it up into segments separated by dots (.).
5. For each segment, if it is a valid qualifier list then add it to qualifiers, otherwise append it to resourceName.
6. Call the equivalent of MrmIndexFile(indexer, resourceName, filePath, qualifiers)

For example:

Note that there is no way to determine what the inferred resourceName and qualifiers are for a given string; they are simply added to the indexer. The only way to determine the values that were inferred is to create the PRI file and then dump it using one of the MrmDump... functions.

Valid file paths

Unlike MrmIndexFile, the filePath argument should be a legal file path, although the file does not need to exist. It should be a relative path, not including a parent directory escape (..\). The projectRoot specified during indexer creation can be used to generate relative file paths. For example, if the indexer was created with a projectRoot of C:\Projects\MyApp and you index the file C:\Projects\MyApp\Assets\file.scale-200.jpg, the function will automatically convert that to the relative filename Assets\file.scale-200.jpg (of course you could just add the relative name Assets\file.scale-200.jpg directly).

There are two important caveats with the validation of the filePath parameter:

1. Using forward slashes (/) instead of backslashes (\) bypasses the checking performed by this function, and can result in illegal filenames in the PRI file.
2. Invalid file paths are not detected when this function is called, but only when the resource file is created on.

Requirements

See also