Skip to content
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

Support equivalent of ComposeExportedValue in System.Composition #18624

Closed
dsplaisted opened this issue Sep 19, 2016 · 10 comments
Closed

Support equivalent of ComposeExportedValue in System.Composition #18624

dsplaisted opened this issue Sep 19, 2016 · 10 comments

Comments

@dsplaisted
Copy link
Member

@dsplaisted dsplaisted commented Sep 19, 2016

System.ComponentModel.Composition (MEF1) has the ability to supply imports to an already-instantiated object, via the ComposeExportedValue<T>(T exportedValue) method. As requested by @ZigMeowNyan and @jabbera in #15362, it would be useful to have this ability in System.Composition (MEF2).

@karelz
Copy link
Member

@karelz karelz commented Nov 23, 2016

We need formal API proposal

@NEKIT-Boss
Copy link

@NEKIT-Boss NEKIT-Boss commented May 4, 2017

Add methods to ContainerConfiguration class:

public ContainerConfiguration WithInstance<TExport> (TExport instance);
public ContainerConfiguration WithInstance<TExport> (string contractName, TExport instance);
public ContainerConfiguration WithInstance (Type t, object instance);
public ContainerConfiguration WithInstance (Type t, string contractName, object instance);
@siobhanc
Copy link

@siobhanc siobhanc commented Jul 31, 2017

Just adding a +1 to this request. Heavily reliant on ComposeExportedValue and without it, or a sensible workaround, will have to completely redesign my system in order to port to .Net Core

@exones
Copy link

@exones exones commented Oct 16, 2017

This is very frustrating lack of functionality, I join @siobhanc in his comment

@pascalpfeil
Copy link

@pascalpfeil pascalpfeil commented Jul 12, 2018

+1 for this

@gthvidsten
Copy link

@gthvidsten gthvidsten commented Apr 27, 2019

+1 (Surprised nothing has happened after 2.5 years!)

@danmosemsft
Copy link
Member

@danmosemsft danmosemsft commented Apr 27, 2019

Nobody has made a formal API proposal. Guidelines for the format are in the docs folder in this repo. Then the API board can review. If approved, we would welcome a PR with tests from the community.

@gthvidsten
Copy link

@gthvidsten gthvidsten commented Apr 27, 2019

@danmosemsft Care to provide a direct link to the guideline?

@msftgits msftgits transferred this issue from dotnet/corefx Jan 31, 2020
@msftgits msftgits added this to the 5.0 milestone Jan 31, 2020
@ericstj
Copy link
Member

@ericstj ericstj commented Jul 9, 2020

I believe this is now tracked with #29400

@ericstj ericstj closed this Jul 9, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
You can’t perform that action at this time.