When I set in VS2017 the "package version" of a .NET Core and activate the nuget creation on build I get a package ending in the value setted in "package version".
This value is also setted as [assembly: System.Reflection.AssemblyInformationalVersionAttribute("{package-version}")].
Now my question:
When I use for ex:
dotnet_csproj:
patch: true
file: '**\*.csproj'
version: '1.2.25'
package_version: '1.2.25.build35-develop'
assembly_version: '1.2.25'
file_version: '1.2.25'
I expect to get a nuget package ending in 1.2.25.build35-develop.nupkg and a [assembly: System.Reflection.AssemblyInformationalVersionAttribute("1.2.25.build35-develop")], but I get a package ending in 1.2.25.nupkg and a [assembly: System.Reflection.AssemblyInformationalVersionAttribute("1.2.25")]
So where is the `package-value` used? Or I am using it wrong?

#1 Posted by Rgomez on 24 Oct, 2018 09:51 PM
When I set in VS2017 the
package-versionof a .NET Core and activate the nuget creation on build I get a package ending in the value setted inpackage-version.This value is also setted as
[assembly: System.Reflection.AssemblyInformationalVersionAttribute("{package-version}")].Now my question:
When I use for ex:
I expect to get a nuget package ending in
1.2.25.build35-develop.nupkgand a[assembly: System.Reflection.AssemblyInformationalVersionAttribute("1.2.25.build35-develop")], but I get a package ending in1.2.25.nupkgand a[assembly: System.Reflection.AssemblyInformationalVersionAttribute("1.2.25")]So where is the
package-valueused? Or I am using it wrong?#2 Posted by Owen McDonnell Support staff on 24 Oct, 2018 10:43 PM
I believe
package_versionis used for nuget packaging. Try to omit it and put the intended version underversion:key.Ilya Finkelshteyn closed this discussion on 25 Dec, 2018 09:00 PM.