We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Continuation from #11.
It would be nice if this could report on packages that are redundant.
For example, a metapackage A depends on package B. If the .csproj references both then you can remove B.
A
B
.csproj
Concrete example:
<PackageReference Include="Serilog.AspNetCore" Version="3.4.0" /> <PackageReference Include="Serilog.Extensions.Hosting" Version="3.1.0" />
Serilog.AspNetCore 3.4.0 depends on Serilog.Extensions.Hosting 3.1.0. Since the latter is already referenced (transitively), it's redundant and can be removed.
The text was updated successfully, but these errors were encountered:
This has to consider the upper version dependencies as they might not be redundant.
An example I have seen.
<PackageReference Include="Confluent.Kafka" Version="1.8.2" /> <PackageReference Include="KafkaFlow" Version="2.2.1" />
KafkaFlow depends on Confluent.Kafka >= 1.7.0 which has an issue with old version of OpenSSL so I would want to target 1.8.2 of Confluent.Kafka
KafkaFlow
Confluent.Kafka
1.8.2
Sorry, something went wrong.
No branches or pull requests
Continuation from #11.
It would be nice if this could report on packages that are redundant.
For example, a metapackage
A
depends on packageB
. If the.csproj
references both then you can removeB
.Concrete example:
Serilog.AspNetCore 3.4.0 depends on Serilog.Extensions.Hosting 3.1.0. Since the latter is already referenced (transitively), it's redundant and can be removed.
The text was updated successfully, but these errors were encountered: