This repository was archived by the owner on Jun 13, 2024. It is now read-only.
Fixing Publish Failure (#510) #567
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Publish fails on poor searching of a nupkg file.
Update of my change with FullName to ensure that correct path will be hand over.
|
Closing in favor of similar changes merged in via PR #613 |
|
@anamnavi Nice, thank you for information. It took only 3 years. 🤣 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Publish fails on poor searching of a nupkg file.
The issue is reported here.
On non en-US environments, MSBuild produces culture variant message.
New-NugetPackagerelies on the English string.The main problem here is a wrong perspective.
We are dealing with a file path as a
stringnot as aFileIOinstance.