confused nuget references #1

Open
opened 2026-01-29 22:03:19 +00:00 by claunia · 0 comments
Owner

Originally created by @sawilde on GitHub (Aug 7, 2013).

I am developing a 'portable' nuget package that references the sharpcompress library however I am having issues when I use my package on .NET40.

My assembly is referencing the sharpcompress.portable assembly but in a .NET40 project the sharpcompress.dll is loaded instead causing a missing reference exception. Manually changing the reference works but is definitely confusing.

Would it be possible to have all your assemblies be called SharpCompress.dll when they are packaged into the nuget package?

Originally created by @sawilde on GitHub (Aug 7, 2013). I am developing a 'portable' nuget package that references the sharpcompress library however I am having issues when I use my package on .NET40. My assembly is referencing the sharpcompress.portable assembly but in a .NET40 project the sharpcompress.dll is loaded instead causing a missing reference exception. Manually changing the reference works but is definitely confusing. Would it be possible to have all your assemblies be called SharpCompress.dll when they are packaged into the nuget package?
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/sharpcompress#1