-
Notifications
You must be signed in to change notification settings - Fork 87
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Questions on using/moving from standard System.Composition #34
Comments
To start off, I'll call out that the caching feature is a proof of concept in its current form. I wouldn't recommend shipping an app that relies on it just yet. We are actively working on finishing that feature though, so I hope soon we can freely encourage people to try it out and ship with it. To your questions:
|
I wrote up some additional docs, including the topic of |
Thanks for your quick responses and demos. I was able to put together a test project with all the ways we used System.Composition so we're on the way. I'm performance testing right now, so hopefully this will bump the speed up. |
I'd love to hear the results of your effort and perf testing. |
Our system is currently using System.Composition for MEF and we'd like to add the caching feature using this package. What isn't clear is how to get this package to work with out existing setup. Here's some issues/questions:
We're using the AggregateCatalog that has both AssemblyCatalogs and a DirectoryCatalog. How do we use a DirectoryCatalog with the ComposableCatalog?
We use an ExportFactory with an ImportMany attribute to create many instances of an exported part. Can we continue to use the ExportFactory or is there another construct that replaces it in this package?
Is there more documentation on the caching? I assume the ExportProviderFactory.LoadDefault() loads from cache, what if things haven't been cached? Where is the actual cache located?
Is there an example project somewhere that has a typical System.Composition MEF scenario and how VS MEF works with it or in place of it?
Thanks!
The text was updated successfully, but these errors were encountered: