Closed rheone closed 4 years ago
This may be a side effect of the way the nuget packages were originally built and released, and may have resolved itself now that we have an appropriate GitHub hash associated.
Verify, but note to self don't pack from internal repository
This issue seems to be resolved, and should be covered in the next release by our current build pipeline.
Any reason not to release to make the issue go away?
I see no issue with a patch change release once we include the current PRs
Source is not available in Visual Studio 2019 community edition.