BattleRush
commented
7 years ago This seems to be a similar issue to dotnet/runtime#17745
Possible fix: https://github.com/dotnet/corefx/issues/9788#issuecomment-288678333
Closed sadeqhatami closed 4 years ago
BattleRush
commented
7 years ago This seems to be a similar issue to dotnet/runtime#17745
Possible fix: https://github.com/dotnet/corefx/issues/9788#issuecomment-288678333
sadeqhatami
commented
7 years ago @BattleRush thank's for answer,i was see this issue and do it but my problem not fix :(
karelz
commented
7 years ago @ericstj @weshaggard is it potentially a bug in our/MS packaging?
ericstj
commented
7 years ago Microsoft.Composition has never supported netcoreapp and that package is not produced out of corefx.
You can exclude Microsoft.Composition and reference System.Composition:
<PackageReference Include="Microsoft.Composition" Version="1.0.27" ExcludeAssets="All" />
<PackageReference Include="System.Composition" Version="1.0.31" />
pnobre
commented
7 years ago I was having the same issue and managed to solve it by removing the offending package. By mistake I have added scaffolding support to one of my mvc projects. This added a reference to Microsoft.VisualStudio.Web.CodeGeneration.Design, which if you follow to nuget references all the way down to Microsoft.CodeAnalysis.Workspaces.Common, will reference Microsoft.Composition. So, in my case, removing the Microsoft.VisualStudio.Web.CodeGeneration.Design package reference, solved the issue.
seanterry42
commented
7 years ago pnobre pointed out where I was seeing this as well. My MVC project had a PackageTargetFallback entry in it, but the error actually showed up when referencing that project from my testing project. Adding the same entry to the test project cleared up the error.
ericstj
commented
7 years ago Closing this as there are several workarounds. I recommend you follow up with the owner of the package that had this dependency Microsoft.CodeAnalysis.Workspaces.Common and ask them to update their package so you don't need to use workarounds.
seanterry42
commented
7 years ago ericstj, just for posterity, it is added to ASP.NET Core projects automatically when taking the following actions:
avikenjale
commented
7 years ago @ericstj : Unable to get rid of "Microsoft.Composition": "1.0.27", as it is no where referenced in project explicitly,
@seanterry42 , this is true. Even after removing Microsoft.VisualStudio.Web.CodeGeneration.Design from .csproj I am getting this issue. I can see *.deps.json, *.assets.json have references of this.
ericstj
commented
7 years ago You don't need to have a direct reference to remove it. The app can use the workaround I mentioned above:
<PackageReference Include="Microsoft.Composition" Version="1.0.27" ExcludeAssets="All" />
<PackageReference Include="System.Composition" Version="1.0.31" />You can also use the imports/PackageTargetFallback workaround with portable-net45+win8+wp8+wpa81.
oliverjanik
commented
7 years ago This is just infuriating, MS left hand does not know what right hand is doing. Death by 1000 paper cuts.
Today I thought I would install Microsoft.CodeAnalysis.CSharp.Workspaces
Guess what:
Package Microsoft.Composition 1.0.27 is not compatible with netcoreapp1.1 (.NETCoreApp,Version=v1.1). Package Microsoft.Composition 1.0.27 supports: portable-net45+win8+wp8+wpa81 (.NETPortable,Version=v0.0,Profile=Profile259)
One or more packages are incompatible with .NETCoreApp,Version=v1.1.Even though the library I wanted to install is declared as netstandard1.3 it fails to install because of this dependency. This is just about 100th item within a month.
Where's the issue? I don't know and don't care. Who's the owner of Microsoft.Composition. Where is their bug tracker? How is your average dev supposed to know who owns what in Micorsoft?
Microsoft released a 1.1 product and we're all beta testers.
AlexGhiondea
commented
7 years ago @oliverjanik I understand how frustrating this is.
I have published an updated version of Microsoft.Composition (1.0.0.31) which pulls in the System.Composition (1.0.0.31) into your project. What this does is it allows for a path forward for packages that are using the Microsoft.Composition packages to move to System.Composition.
Could you try this?
This should ensure that the packages will correctly resolve.
oliverjanik
commented
7 years ago @AlexGhiondea That works! Thanks for acting so quickly.
Now you just need to push this to nuget.org and get Microsoft.CodeAnalysis.CSharp.Workspaces to depend on the new version ;-)
AlexGhiondea
commented
7 years ago @oliverjanik thanks for confirming that this solved your issue!
alexsorokoletov
commented
7 years ago +1 for the Microsoft.CodeAnalysis.CSharp.Workspace update
aka-STInG
commented
7 years ago Also looking forward to get fix on nuget
AlexGhiondea
commented
7 years ago The package has been pushed to Nuget.org.
RandyBuchholz
commented
7 years ago Added a workaround to https://github.com/aspnet/Tooling/issues/1051
ghost
commented
7 years ago This is my csproj, where is it getting the idea that I need Microsoft.Composition?
<Project Sdk="Microsoft.NET.Sdk">
<PropertyGroup>
<TargetFramework>netcoreapp1.1</TargetFramework>
<IsPackable>false</IsPackable>
</PropertyGroup>
<ItemGroup>
<EmbeddedResource Include="Blueprints\brian.json" />
</ItemGroup>
<ItemGroup>
<PackageReference Include="Microsoft.AspNetCore.TestHost" Version="1.1.3" />
<PackageReference Include="xunit" Version="2.3.0" />
</ItemGroup>
<ItemGroup>
<ProjectReference Include="..\Subscription.Services.EloquaImport\Subscription.Services.EloquaImport.csproj" />
</ItemGroup>
</Project>It might be a transitive reference. Can you try the workaround called out above?
ghost
commented
7 years ago Why doesn't the error message tell me what transitive references are causing the problem?
On Fri, Oct 13, 2017 at 1:56 PM, Alex Ghiondea notifications@github.com wrote:
It might be a transitive reference. Can you try the workaround called out above?
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/dotnet/corefx/issues/18452#issuecomment-336565143, or mute the thread https://github.com/notifications/unsubscribe-auth/AX5XbueAZACC4y8px8tQkPfkxBKtIw0iks5sr855gaJpZM4M-mcx .
-- CONFIDENTIALITY NOTICE: The contents of this email message and any attachments are intended solely for the addressee(s) and may contain confidential and/or privileged information and may be legally protected from disclosure. It is then shared with tech companies, bots, hackers, government agencies, and marketers. The security of this message is none, and it may be shared on Instagram at anytime. If you are OK with this, please respond. There isn't really any security or privacy anywhere. If you disagree you may want to go camping and talk to people face-to-face like in old times.
cbruen1
commented
6 years ago Adding a reference to Microsoft.Composition 1.0.0.31 solved it for me. I didn't need to add a reference to Microsoft.CodeAnalysis.CSharp.Workspaces - should I?
hello i use VS 2017 version 15.1 (26403.3) Release and .Net framework version 4.6.01586 when i build my project build succeed and my project is lunch,but in Error List i see this error
my csproj is
how i can fix this problem?