allow packages.config update when project file doesn't list assembly version #9534
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
brettfo
force-pushed
the
dev/brettfo/packages-config-without-assembly-version
branch
from
d93a835
to
1b2f69d
Compare
ryanbrandenburg
approved these changes
Apr 18, 2024
abdulapopoola
deleted the
dev/brettfo/packages-config-without-assembly-version
branch
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 updating in a
packages.configscenario, the.csprojdoesn't have to list the assembly version. This modifies the check to allow eitherInclude="Some.Dependency"orInclude="Some.Dependency, Version=1.2.3.4, ....".