StrongName Microsoft.Android.Build.BaseTasks #127
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dellis1972
commented
Jul 19, 2021
|
|
||
| <PropertyGroup> | ||
| <TargetFramework>netstandard2.0</TargetFramework> | ||
| <TargetFrameworks>netstandard2.0;netcoreapp3.1</TargetFrameworks> |
Contributor
Author
There was a problem hiding this comment.
Had to do this to work around
error CS1705: Assembly 'Microsoft.Android.Build.BaseTasks' with identity 'Microsoft.Android.Build.BaseTasks, Version=1.0.0.0, Culture=neutral, PublicKeyToken=84e04ff9cfb79065' uses 'libZipSharp, Version=1.0.7866.25205, Culture=neutral, PublicKeyToken=276db85bc4e20efc' which has a higher version than referenced assembly 'libZipSharp' with identity 'libZipSharp, Version=1.0.7866.25201, Culture=neutral, PublicKeyToken=276db85bc4e20efc'
Which is odd. But 🤷
jonathanpeppers
approved these changes
Jul 19, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Let's StrongName our assemblies.