tag:blogger.com,1999:blog-393540894130950585.post6323742159422183231..comments2024-03-22T00:23:29.865-07:00Comments on Never In Doubt: DevForce Extensibility With MEF InheritedExportWard Bellhttp://www.blogger.com/profile/10977457957771020146noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-393540894130950585.post-1338282469388882162010-04-04T07:03:46.398-07:002010-04-04T07:03:46.398-07:00Yes Wim, they would have to use Import.
However, ...Yes Wim, they would have to use Import.<br /><br />However, the primary use case for InheritedExport is for existing infrastructure which is migrated to use MEF. In those cases it is likely the contract types express that services or a locator.Glenn Blockhttp://blogs.msdn.com/gblocknoreply@blogger.comtag:blogger.com,1999:blog-393540894130950585.post-74846246543149803712010-04-03T13:37:51.930-07:002010-04-03T13:37:51.930-07:00Good observation about what my customer would need...Good observation about what my customer would need to do to import parts into his/her exported customization.<br /><br />Our prior extensibility mechanism did not inject parts into customer extensions so this is not a migration issue. <br /><br />I can imagine us enabling injection scenarios in future ... and these likely would require MEF import attributes on the custom part.<br /><br />Our extensibility interfaces today typically prescribe methods whose parameters are set by DevForce. For example, DevForce supplies the user Principal as an argument to a query checking method.<br /><br />I'm not seeing the need to inject anything into the extension just yet ... but its great to know we could.Ward Bellhttps://www.blogger.com/profile/10977457957771020146noreply@blogger.comtag:blogger.com,1999:blog-393540894130950585.post-4925970770556009982010-04-03T09:38:58.372-07:002010-04-03T09:38:58.372-07:00Interesting, I knew about InheritedExport but had ...Interesting, I knew about InheritedExport but had not yet realized it could be applied to the contract interface itself!<br /><br />However, your customer will still need to know about MEF attributes anyway if he needs to import other parts in his customized part. To eliminate the need for import attributes as well, I guess you'd have to write a custom export provider implementation.Wim Coenenhttps://www.blogger.com/profile/16314282132983289163noreply@blogger.com