You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When upgrading to .NET9, we had to add some explicit references to packages that previously were implicit.
The ones referencing these were using old versions, and because of new analyzer updates in .NET9 we get warnings for vulnerabilities in these versions, and warnings are errors!
So we either had to disable <TreatWarningsAsErrors> or disable the warnings, both bad options.
The least bad option is to explicitly upgrade all of these NuGets.
They should be removed once the ones making the implicit references happen have updated their NuGets.
These Nugets:
System.Text.Json
System.Drawing.Common
Microsoft.IdentityModel.JsonWebTokens
System.IdentityModel.Tokens.Jwt
System.Formats.Asn1
in these projects:
Application Integration Tests
SlackNotifier
Utils AspNet
WebAPI
Infrastructure
CDC
The text was updated successfully, but these errors were encountered:
<!--- Provide a general summary of your changes in the Title above -->
## Description
<!--- Describe your changes in detail -->
## Related Issue(s)
- #1467
## Verification
- [ ] **Your** code builds clean without any errors or warnings
- [ ] Manual testing done (required)
- [ ] Relevant automated test added (if you find this hard, leave it and
we'll help out)
## Documentation
- [ ] Documentation is updated (either in `docs`-directory, Altinnpedia
or a separate linked PR in
[altinn-studio-docs.](https://github.com/Altinn/altinn-studio-docs), if
applicable)
When upgrading to .NET9, we had to add some explicit references to packages that previously were implicit.
The ones referencing these were using old versions, and because of new analyzer updates in .NET9 we get warnings for vulnerabilities in these versions, and warnings are errors!
So we either had to disable
<TreatWarningsAsErrors>
or disable the warnings, both bad options.The least bad option is to explicitly upgrade all of these NuGets.
They should be removed once the ones making the implicit references happen have updated their NuGets.
These Nugets:
in these projects:
The text was updated successfully, but these errors were encountered: