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

ImportMany collection property has no setter, and it is always empty in the runtime. #118

Open
lifengl opened this issue Mar 7, 2019 · 3 comments
Assignees

Comments

@lifengl
Copy link
Member

lifengl commented Mar 7, 2019

I remember the bug #94 was fixed. But when I removed 'set', and imported collection becomes empty. I noticed it in a recent d16.0stg build.

@AArnott
Copy link
Member

AArnott commented Mar 7, 2019

We have a test for what you describe:

https://github.com/Microsoft/vs-mef/blob/4bcbb4f5d7f02f91f4b1623911fc1bd727bcaa72/src/tests/Microsoft.VisualStudio.Composition.Tests/RejectionTests.cs#L101-L106

What is different about your case that leads it to fail?

@lifengl
Copy link
Member Author

lifengl commented Mar 9, 2019

interesting, I hit this problem on a head of a MEF scope (UnconfiguredProjectImpl), so it is coming from ExportFactory.CreateExport(). I wonder whether that makes any difference.

@AArnott
Copy link
Member

AArnott commented Mar 11, 2019

Would you be willing to try adding a test for it to see if you can repro it?

AArnott added a commit that referenced this issue Jun 7, 2022
Update to latest dotnet-install script
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants