diff options
author | Matt Ward <matt.ward@xamarin.com> | 2015-08-25 18:40:57 +0300 |
---|---|---|
committer | Matt Ward <matt.ward@xamarin.com> | 2015-08-25 18:40:57 +0300 |
commit | acc21495f4eefc052737cc0ede36e208c1c39467 (patch) | |
tree | 8dcd45837892e2637bd1dd0b1521cf790c2e060b /main/external | |
parent | d3e6e35b98ada693e7ac16f3597886a583af294b (diff) |
[NuGet] Allow Microsoft.ApplicationInsights to be installed
Fixed bug #30049 - Unable to install Microsoft.ApplicationInsights
https://bugzilla.xamarin.com/show_bug.cgi?id=30049
The Microsoft.ApplicationInsights NuGet package specifies a
minClientVersion of 2.8.50313 which is the version of the NuGet
Package Manager's assembly version released by Microsoft but not the
production version which is 2.8.1. NuGet.Core when built for
MonoDevelop uses the same version for both of these values and does
not match the version generated by Microsoft.
The Microsoft.ApplicationInsights NuGet package seems to be the only
NuGet package that uses the assembly version. Other NuGet packages
produced by teams at Microsoft use the product version when specifying
the minClientVersion.
To handle this the 2.8.50313 version is mapped to 2.8.1. Another
alternative fix would have been to change the assembly version to
match the one generated by Microsoft. However most of the existing
NuGet packages are incorrectly using the product version as the
minClientVersion, so they would install into project when the NuGet
product version was not high enough since the check is made against
the assembly version. This problem only seems to have started since
NuGet started using 3 numbers for the 2.8.* releases. The third
number in the assembly version is based on the date the assembly
was built.
Diffstat (limited to 'main/external')
m--------- | main/external/nuget-binary | 0 |
1 files changed, 0 insertions, 0 deletions
diff --git a/main/external/nuget-binary b/main/external/nuget-binary -Subproject 81cc5eccc3b004c5f07d8f2c783590caa9dd554 +Subproject 4612ea9166f27f5193b4abb3c0825e52df08eb8 |