Merges into the current scope all the metadata scopes specified by one or more prior calls to IMetaDataEmit::Merge.
This method takes no parameters.
This routine triggers the actual merge of metadata, of all import scopes specified by preceding calls to IMetaDataEmit::Merge, into the current output scope.
The following special conditions apply to the merge:
A module version identifier (MVID) is never imported, because it is unique to the metadata in the import scope.
No existing module-wide properties are overwritten.
If module properties were already set for the current scope, no module properties are imported. However, if module properties have not been set in the current scope, they are imported only once, when they are first encountered. If those module properties are encountered again, they are duplicates. If the values of all module properties (except MVID) are compared and no duplicates are found, an error is raised.
For type definitions (TypeDef), no duplicates are merged into the current scope. TypeDef objects are checked for duplicates against each fully-qualified object name + GUID + version number. If there is a match on either name or GUID, and any of the other two elements is different, an error is raised. Otherwise, if all three items match, MergeEnd does a cursory check to ensure the entries are indeed duplicates; if not, an error is raised. This cursory check looks for:
The same member declarations, occurring in the same order. Members that are flagged as mdPrivateScope (see the CorMethodAttr enumeration) are not included in this check; they are merged specially.
The same class layout.
This means that a TypeDef object must always be fully and consistently defined in every metadata scope in which it is declared; if its member implementations (for a class) are spread across multiple compilation units, the full definition is assumed to be present in every scope and not incremental to each scope. For example, if parameter names are relevant to the contract, they must be emitted the same way into every scope; if they are not relevant, they should not be emitted into metadata.
The exception is that a TypeDef object can have incremental members flagged as mdPrivateScope. On encountering these, MergeEnd incrementally adds them to the current scope without regard for duplicates. Because the compiler understands the private scope, the compiler must be responsible for enforcing rules.
Relative virtual addresses (RVAs) are not imported or merged; the compiler is expected to re-emit this information.
Custom attributes are merged only when the item to which they are attached is merged. For example, custom attributes associated with a class are merged when the class is first encountered. If custom attributes are associated with a TypeDef or MemberDef that is specific to the compilation unit (such as the time stamp of a member compile), they are not merged and it is up to the compiler to remove or update such metadata.
Platforms: See .NET Framework System Requirements.
Library: Used as a resource in MSCorEE.dll
.NET Framework Versions: Available since 1.1