-
Notifications
You must be signed in to change notification settings - Fork 10
Use Central Package Management 8000 bdi> #125
New issue
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
Use Central Package Management #125
Conversation
Instead of using custom <Import Project=...> use the standard [Central Package Management](https://learn.microsoft.com/en-us/nuget/consume-packages/central-package-management) mechanism.
> warning NU1507: There are 3 package sources defined in your configuration. When using central package management, please map your package sources with package source mapping (https://aka.ms/nuget-package-source-mapping) or specify a single package source. The following sources are defined: nuget.org, AnotherSource, YetAnotherSource
> warning NU1903: Package 'Newtonsoft.Json' 10.0.1 has a known high severity vulnerability, GHSA-5crp-9r3c-p9vr
Something apparently changed in the runtime when boxing enums values with multiple definitions sharing the same values such as HttpStatusCode. E.g. HttpStatusCode.Ambiguous == HttpStatusCode.MultipleChoices == 300
Looks great, thanks! Do you mind not targeting NET9.0 yet? AppVeyor did not yet update their build image https://www.appveyor.com/docs/windows-images-software/#visual-studio-2022 |
I've closed #124, we can merge this one. |
I just removed .NET 9 support in eb40ffc, let's see how it goes on AppVeyor. |
I also had to remove .NET 5 and now everything is ✅ on AppVeyor. |
Many thanks, Cédric! A new release is on the way. |
Instead of using custom
<Import Project=…>
use the standard Central Package Management mechanism.Also add tests on .NET 8 and 9 and fix many warnings.
I should have looked at existing pull requests first because there's some overlap with #124.