dotnet build (1.0.0-rc2-002543) - An item with the same key has already been added. Key: System.IO.Compression
See original GitHub issueSteps to reproduce
Clone https://github.com/Humanizr/Humanizer.git and checkout the dev branch. Checkout this commit: https://github.com/Humanizr/Humanizer/commit/c42e2cd03356824e7a68f93753c22c01143393ac
go to src\Humanizer and run restore on Humanizer and Humanizer.Tests.Dotnet
in src\Humanizer.Tests.DotNet, run dotnet build
Expected behavior
Build should succeed.
Actual behavior
Build fails with An item with the same key has already been added. Key: System.IO.Compression
Environment data
dotnet --info
output:
.NET Command Line Tools (1.0.0-rc2-002543)
Product Information: Version: 1.0.0-rc2-002543 Commit Sha: 38d0c28a1e
Runtime Environment: OS Name: Windows OS Version: 10.0.14332 OS Platform: Windows RID: win10-x64
Issue Analytics
- State:
- Created 7 years ago
- Comments:26 (26 by maintainers)
Top Results From Across the Web
An item with the same key has already been added
Most likely, you have model which contains the same property twice. Perhaps you are using new to hide the base property.
Read more >An item with the same key has already been added
I always receive this error "An item with the same key has already been added." when I try to start a pipeline release...
Read more >Unknown build error, 'An item with the same key has already ...
I got this error today when trying to build a C# solution today. In my case the error was caused by the fact...
Read more >ZipFile Class (System.IO.Compression)
Provides static methods for creating, extracting, and opening zip archives. ... NET Framework app, you must add a reference to the System.IO.Compression.
Read more >Why I get "an item with the same key has already been ...
I deployed my new bilingual ASP.NET Core website as Azure WebApp. Currently i'm getting from time to time: Expand ▽.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Okay, it’s looking like we’ll need to debug.
cc @piotrpMSFT This seems pretty weird, I think we should consider this for RC2.
Might this have something to do with xproj -> csproj refs?
This is wrong. Humanizer.DotNet.xproj uses project.json. The csproj Humanizer uses Humanizer.project.json and both should not be picked up here.