I just upgraded from 5.6.3 to 5.7.1 via nuget in a visual studio 2019 asp.net mvc solution with several projects.

The app.config files are getting updated differently.

In one project the app.config is upgraded to this: <bindingRedirect oldVersion="0.0.0.0-5.7.0.0" newVersion="5.7.0.0" />

In the other projects the app.config/web.config files are upgraded to this: <bindingRedirect oldVersion="0.0.0.0-5.6.0.0" newVersion="5.6.0.0" />

See screenshot.

Can I/should I manually upgrade the bindingRedirect node in the .config files to <bindingRedirect oldVersion="0.0.0.0-5.7.0.0" newVersion="5.7.0.0" />

Thanks in advance.

/Morten

The binding redirects are added by nuget / vs, not our code, so we don't have any influence over that. In practice you really don't need them, as you use the same version everywhere, right?

The 5.6.0.0 one that's still there might indicate vs got it wrong and didn't upgrade a particular project properly. It might help to e.g. reload the solution (close vs and reload), as that's the only way I sometimes can resolve package version mismatches. (with various nuget packages not related to ours)

Hmm. I see. All projects are upgraded to 5.7.1 only changes to the entries in the .config files do not reflect the version correctly. I guess VS didn't upgrade correctly last time around.

I will try a manual edit.

Thanks for your reply

Otis wrote:

The binding redirects are added by nuget / vs, not our code, so we don't have any influence over that. In practice you really don't need them, as you use the same version everywhere, right?

The 5.6.0.0 one that's still there might indicate vs got it wrong and didn't upgrade a particular project properly. It might help to e.g. reload the solution (close vs and reload), as that's the only way I sometimes can resolve package version mismatches. (with various nuget packages not related to ours)