Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Version for satellite assemblies not generated correctly when using `dotnet build`
See original GitHub issueWhen using NB.GV with a package that has satellite assemblies, the version numbers there are 0.0.0.0
For a repro, see the dev branch of https://github.com/humanizr/Humanizer. This worked before using the regular SDK style version property.
Perhaps with SDK style projects, NB.GV shouldn’t write its own .Version.cs file like it does today? It could just set the appropriate MSBuild properties and let the SDK style tasks generate the attributes in the assembly info file. That may fix the incremental build issue too.
Issue Analytics
- State:
- Created 6 years ago
- Comments:11 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Thanks. That’s very helpful. I can repro the problem. I’ll take a look at the logs and see what’s going on.
NB.GV already sets that property: https://github.com/AArnott/Nerdbank.GitVersioning/blob/master/src/Nerdbank.GitVersioning.NuGet/build/Nerdbank.GitVersioning.targets#L28
But there is a bug in .NET SDK .targets’ ability to restore packages and regenerate their file that causes issues. I’ll share the link later today.