Was this page helpful?
Your feedback about this content is important. Let us know what you think.
Additional feedback?
1500 characters remaining
Export (0) Print
Expand All
Important This document may not represent best practices for current development, links to downloads and other resources may no longer be valid. Current recommended version can be found here.

no_registry

no_registry tells the compiler not to search the registry for type libraries imported with #import.


#import filename no_registry

Parameters

filename

A type library.

If a referenced type library is not found in the include directories, the compilation will fail even if the type library is in the registry. no_registry propagates to other type libraries implicitly imported with auto_search.

The compiler will never search the registry for type libraries that are specified by file name and passed directly to #import.

When auto_search is specified, the additional #imports will be generated with the no_registry setting of the initial #import (if the initial #import directive was no_registry, an auto_search-generated #import is also no_registry.)

no_registry is useful if you want to import cross referenced type libraries without the risk of the compiler finding an older version of the file in the registry. no_registry is also useful if the type library is not registered.

Community Additions

ADD
Show:
© 2015 Microsoft