I'm using the NuGet package Squid-Box.SevenZipSharp in a .NET 4.8 application that is deployed via MSI. After updating from NuGet package version 1.3.283 to 1.5.0.366 I noticed a strange behaviour in the update process of my application. This is caused by the versions of the 1.5.0.366 package being all set to 1.0.0.0, whereas the versions were set correctly in the old version:
File squid-box.sevenzipsharp.1.5.0.366\lib\net45\SevenZipSharp.dllAssembly name SevenZipSharp, Version=1.0.0.0, Culture=neutral, PublicKeyToken=c8ff6ba0184838bb
It seems AppVeyor is used to build the NuGet packages and after a quick Googling the config should also look good with dotnet_csproj/patch (although I have to admit that I have no experience with AppVeyor). Do you have any idea where the problem could come from or could I somehow assist fixing it?
I'm using the NuGet package Squid-Box.SevenZipSharp in a .NET 4.8 application that is deployed via MSI. After updating from NuGet package version 1.3.283 to 1.5.0.366 I noticed a strange behaviour in the update process of my application. This is caused by the versions of the 1.5.0.366 package being all set to 1.0.0.0, whereas the versions were set correctly in the old version:
File
squid-box.sevenzipsharp.1.5.0.366\lib\net45\SevenZipSharp.dll
Assembly name SevenZipSharp, Version=1.0.0.0, Culture=neutral, PublicKeyToken=c8ff6ba0184838bb
File
squid-box.sevenzipsharp.1.3.283\lib\net45\SevenZipSharp.dll
Assembly name SevenZipSharp, Version=1.3.283.0, Culture=neutral, PublicKeyToken=c8ff6ba0184838bb
It seems AppVeyor is used to build the NuGet packages and after a quick Googling the config should also look good with
dotnet_csproj
/patch
(although I have to admit that I have no experience with AppVeyor). Do you have any idea where the problem could come from or could I somehow assist fixing it?