Unexpected git hash commit in Nuget package version

[Woudjee]

Hi,

I have been experimenting with the automatic creation of Nuget packages in my Azure DevOps pipeline and have been running into an issue where the git commit hash is added to the version of my Nuget package. For me, this is unexpected behaviour. I have spent a lot of time trying to understand how to change this. After not being succesful, I postponed working on this.

Today I continued and pushed my first .NET Core Nuget package (as well as a .NET Framework package). I guess the screenshot below explains well which one is which. It really drew my attention that the .Core Nuget does not have the git commit hash.

Both projects use the SDK .csproj setup and are identical except for some package references. See below:

Question: how do I remove the git commit hash from my Nuget version for my .NET Framework (or .NET Standard) Nuget package?

Thank you for your suggestions!

Woudjee

[baronfel]

See the breaking change documentation for .NET 8 here to learn more about this change and how to change it.

[Woudjee]

Omg it had to be something as simple as this. I will try it out straight away!

[Woudjee]

Btw, this works as expected now! :D