The license is for the whole feature. In my case each application implements an interface if you will IFeature and before i import this I feature into my host i would like to check with our licensemanager if this feature is licensed.
If it is not licensed i want to make sure that this feature interface is not available for consumption, so the entire type is not available. Ideally i would like to do this before the component is created. In MEF when types are imported are those types created
right upfront (all assemblies laoded and types created) or they loaded on demand. If they are demand loaded i can potentially implement my license checks at the point before the types are created.

Types are not instantiated until they are actually needed and catalogs are the key point where assembly loading occurs. Within a custom catalog, you can
apply custom filtering as to which assemblies / types will be loaded. I’d recommend looking into creating a custom catalog that internally scans and determines which assemblies / types the license allows and creates Type/Assembly catalogs to load the parts
in.

The license is for the whole feature. In my case each application implements an interface if you will IFeature and before i import this I feature into my host i would like to check with our
licensemanager if this feature is licensed. If it is not licensed i want to make sure that this feature interface is not available for consumption, so the entire type is not available. Ideally i would like to do this before the component is created. In MEF
when types are imported are those types created right upfront (all assemblies laoded and types created) or they loaded on demand. If they are demand loaded i can potentially implement my license checks at the point before the types are created.