Version number in assembly name does not match package

[twsouthwick]

It's helpful when these match (or at least are close). The 6.1.0 package says its 4.9.4.0. Ideally, this would be either 6.1.0.0 so it's easy to correlate which package it came from. I've often used GitVersion or Nerdband.Versioning to accomplish this. Any thoughts?

[robdmoore]

We are using git version: https://github.com/MRCollective/AppVeyorConfig. I noticed some build warnings. I think the problem is 4.9.0 is hard coded in the .csproj. We should remove that and it should all fix itself up I think.

…

--

On 8 Oct 2020, at 12:15 am, Taylor Southwick ***@***.***> wrote:  It's helpful when these match (or at least are close). The 6.1.0 package says its 4.9.4.0. Ideally, this would be either 6.1.0.0 so it's easy to correlate which package it came from. I've often used GitVersion or Nerdband.Versioning to accomplish this. Any thoughts? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or unsubscribe.