fix Ambiguous project name error while restoring NuGet packages.
#1027
Conversation
This file contains 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
Make all csproj PackageId-s empty.
|
Looks the following files also need to be changed. Can you update them as well?
|
|
The *.Core.csproj files didn't have the problem, so we don't need to change them. |
|
LGTM |
|
Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When I had tried to build NPOI.sln with VS2022, I always got
Ambiguous project name 'NPOI'error while restoring NuGet packages. Therefore, I was able able to test only NPOI.Core build until recently.After some search I found NuGet/Home#7372 that says all csproj files should have unique or empty PackageId.
So I removed all
<PackageId>NPOI</PackageId>settings from csproj files to resolve the ambiguous project name error.