A Smart Document solution is likely to contain numerous
files—help files, templates, XSL transformations, document
fragments, and media clips, not to mention the actual
.dll, manifest file, and schema. Each of these
files should be listed in the manifest; when the expansion pack is
attached to the document or template, the application will check to
ensure that it can locate each referenced file.
It is important to note, however, that the references to these files in the .dll must be absolute pathnames or URLs. If the Smart Document solution cannot locate a referenced file, it will just ignore it. Building in some error checking to test that the files actually exist in the designated file locations is highly recommended.
One method for resolving the
absolute pathname is to set a constant to the installation directory
of the Smart Document solution in the
method. By prepending this constant to the specific directory and
filename, the files can be located by the application and the
developer does not have to worry about where they were actually
If a specific installation directory is not given in the manifest file, the solution is loaded in the schema folder under the Application Data folder in the user’s Documents and Settings folder (C:\Documents and Settings\<username>\Local Settings\Application Data\Microsoft\Schemas).
Subdirectories appear to be flattened when copied to the installation directory; that is, if you created subdirectories ...