In my scenario the path of the application don't contains any dll.
The application overrides OnResolveAssembly granting that all work good and loading the dlls from others path.
Except the RadRichTextBox!
How to adopt a similar strategy with MEF and assign dinamically the dll positions?
Solved using RadCompositionInitializer.Catalog = new TypeCatalog(..) strategy.
Now, how to know requested type [that will change with RichTextBox releases]?
Is not possible to create the type catalog from the current RadCompositionInitializer.Catalog parts?
Or introduce a method RadCompositionInitializer.ReloadCatalog() or something similar?
answered on 16 Dec 2014, 05:10 PM
RadRichTextBox uses MEF to load its extensible components - the dialogs in the UI, context menu, etc. All types loaded by MEF are listed here and I'm afraid there is no way to obtain them with code. My suggestion to you is to add them in your application just before the initialization of RadRichTextBox.
The fact is RadRichTextBox is pretty feature-complete in terms of UI, so we do not introduce new dialogs with every release. On the chance that this happens, it will be noted in the release notes of the version and the respective articles for the control - Changes and Backward Compatibility. I'll also forward your feedback to the team and we will consider introducing some mechanism that will fit your scenario.
Check out the Telerik Platform - the only platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native mobile apps.