Overview
| Artifact ID: | 06611dfd8d75e440fbfdc6d2f907e7f124e8b9cf |
|---|---|
| Ticket: | c342197be6ac2cae4e8a3283a8fc66334266a30d
DLL version in package 1.0.112.2 is still 1.0.112.1 |
| User & Date: | mistachkin 2020-05-23 23:52:51 |
Changes
- icomment:
This is by design. The source code was not changed between release 1.0.112.1 and 1.0.112.2. Only the NuGet packages were changed. I have not seen the issue with Visual Studio using binding redirects before; however, it seems like an issue specific to Visual Studio, i.e. as far as I know, there is no requirement for a NuGet package version to exactly match that of the managed assemblies contained within it.
- login: "mistachkin"
- mimetype: "text/x-fossil-plain"
- priority changed to: "Medium"
- resolution changed to: "External_Bug"
- status changed to: "Pending"
- subsystem changed to: "NuGetPackage"
- type changed to: "Incident"