Enable Central Package Management for NuGet Dependencies #1124
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
|
The build is failed, could you please recheck |
|
I have built the project on my side, and everything is working fine without any build errors. Could you please share the exact error message you are getting? It might be a dependency/version mismatch. If you have any specific logs or error details, please share them so that I can help debug the issue.
|
|
We might need to change the Azure Pipeline, coz @thiennn is not active for awhile |
|
Why it's closed? |
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.
This PR enables Central Package Management (CPM) for NuGet dependencies in the solution. The following changes were made:
Added Directory.Packages.Props to manage package versions centrally.
Removed individual package version specifications from project files (.csproj).
Ensured compatibility across all projects in the solution.
Why this is needed:
Simplifies package version management across multiple projects.
Ensures consistency and avoids version conflicts.
Makes dependency updates easier by modifying a single file.
Testing:
Verified that the solution builds successfully.
Checked that all projects reference the correct package versions.