Open joelverhagen opened 8 years ago
I can confirm the same using NuGet 4.3.0.4406. Fortunately, the <version>
element in the symbols package does have the suffix so the workaround is just to rename the symbols file and add the suffix manually.
Considering tomorrow is this issue's first anniversary, it would be nice to get an ETA as a gift. 😄
so the workaround is just to rename the symbols file and add the suffix manually.
Another workaround is to use a replacement token, like so:
<version>1.0.0$VersionSuffix$</version>
And then instead of using -Suffix
, use -Properties VersionSuffix=-beta1
.
This isn't a high priority item for now and besides there are easy workarounds available. So will mark it for upforgrab.
Ok it's not prioritary since there are workarounds, but it's a malfunction anyway. Solving using @atifaziz second workaround.
This issue is still active. This is a friendly "bump"
"bumb"
Steps
nuget.exe pack
won't make an empty package).nuget.exe pack path\to\my.nuspec -symbols -suffix beta
Expected
Two nupkgs, one ending in
beta.nupkg
and the other ending inbeta.symbols.nupkg
.Actual
The symbols package's file name has the version number without the suffix. The .nuspec inside the package seems fine though.
Example
Tried on latest
dev
and3.5.0-rc1
.