Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
Ship update to Microsoft.Composition #14653
With #6598 we've decided to discontinue the package
In order to pull customers forward, we should:
Without this, customers will be surprised if they use
@davidfowl We only renamed this package because the actual assemblies inside of it have always had a different name ("System.Composition.*"). It's an attempt to make things consistent.
The other "Microsoft.*" packages already have assemblies with matching names, so there's no need to change them.
Yes, there is two types of packages:
We don't need to make any changes to packages in the second category, but we do need to make changes for the first. And except for
No, unless we shipped said forwarding update :-)
I'm seeing some problems that might be related to this. I'm using Roslyn 2.0 bits in a 4.6.2 library and attempting to create an
So okay, no problem, I'll just uninstall `Microsoft.Composition" and install "System.Composition" instead:
I went ahead and installed
But, wait! It's not over yet. Now that I've got
At this point I'm lost. Do my binding problems look like they're related to CoreFx and the library packaging or is this really an issue with Roslyn/MSBuildWorkspace?
I've gotten my problems worked out - probably not related to this issue after all.
I was using
Sorry for hijacking the issue!
referenced this issue
Jun 12, 2017
This issue was fixed by us shipping https://www.nuget.org/packages/Microsoft.Composition/1.0.31.