-
Notifications
You must be signed in to change notification settings - Fork 483
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
confused nuget references #2
Comments
No problem. I'll release again after I can merge the pull request. Thanks! |
Okay I'll update my nuget package to reference your new one once this is done. Can't wait. |
Cool. Just let me know when. |
After you've published your nuget package so I can reference the version number. From: Adam Hathcockmailto:[email protected] Cool. Just let me know when. Reply to this email directly or view it on GitHub: |
Ensure the assemblies have the same name in the nuget package #2
Released 0.10.1.1...hopefully this behaves better for you. |
1) disabled requirement of signature 2) added runtime discovery of folder with archives changes by this commit are already present in 13ef1c3
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?
The text was updated successfully, but these errors were encountered: