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? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Steps to reproduce
<TargetFrameworks>net6.0;net7.0;net8.0</TargetFrameworks>
<ItemGroup Condition="'$(TargetFramework)' == 'net8.0'"> <PackageReference Include="Microsoft.Net.Http.Headers" Version="8.0.2" /> </ItemGroup> <ItemGroup Condition="'$(TargetFramework)' == 'net7.0' Or '$(TargetFramework)' == 'net6.0'"> <PackageReference Include="Microsoft.Net.Http.Headers" Version="2.2.8" /> </ItemGroup>
Expected behavior I think the best default would be to just check the latest framework. Probably add a command line argument to specify the framework.
Observed behavior ArgumentException: An item with the same key has already been added. Key: Microsoft.Net.Http.Headers
The text was updated successfully, but these errors were encountered:
👍 same as #181: at the very least, it shouldn't crash!
I think, given the complexity, initially the app should just respond stating that multiple target frameworks aren't supported.
Sorry, something went wrong.
No branches or pull requests
Steps to reproduce
<TargetFrameworks>net6.0;net7.0;net8.0</TargetFrameworks>
Expected behavior
I think the best default would be to just check the latest framework. Probably add a command line argument to specify the framework.
Observed behavior
ArgumentException: An item with the same key has already been added. Key: Microsoft.Net.Http.Headers
The text was updated successfully, but these errors were encountered: