Skip to content

Conversation

rolfbjarne
Copy link
Member

nupkg filenames don't contain the metadata from the package version, so compute filenames without the metadata.

This naming behavior can be tested like this:

$ mkdir nupkgtest && cd nupkgtest
$ dotnet new classlib
[...]

$ dotnet pack -p:PackageVersion=3.14
[...]
$ ls **/*.nupkg
bin/Release/nupkgtest.3.14.0.nupkg

$ rm -rf bin obj
$ dotnet pack -p:PackageVersion=2.718+metadata
[...]
$ ls **/*.nupkg
bin/Release/nupkgtest.2.718.0.nupkg

This hopefully fixes a problem where arcade fails to find packages:
https://dev.azure.com/devdiv/DevDiv/_build/results?buildId=10082514&view=logs&j=ba23343f-f710-5af9-782d-5bd26b102304&t=74531eb2-9b39-5603-839e-94e3ba212b65

To double check:

nupkg filenames don't contain the metadata from the package version, so compute filenames without the metadata.

This naming behavior can be tested like this:

```shell
$ mkdir nupkgtest && cd nupkgtest
$ dotnet new classlib
[...]

$ dotnet pack -p:PackageVersion=3.14
[...]
$ ls **/*.nupkg
bin/Release/nupkgtest.3.14.0.nupkg

$ rm -rf bin obj
$ dotnet pack -p:PackageVersion=2.718+metadata
[...]
$ ls **/*.nupkg
bin/Release/nupkgtest.2.718.0.nupkg
```

This hopefully fixes a problem where arcade fails to find packages:
https://dev.azure.com/devdiv/DevDiv/_build/results?buildId=10082514&view=logs&j=ba23343f-f710-5af9-782d-5bd26b102304&t=74531eb2-9b39-5603-839e-94e3ba212b65
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant