Consider using Central Package Management insted of props files

[rstm-sf]

Is your feature request related to a problem? Please describe. At the moment, when adding or bumping any nuget dependency, we need to know about props files

Describe the solution you'd like Central Package Management in my opinion is a mature solution to start using it. This is convenient, everything is stored in one file, and when adding a dependency outside of PackageVersion, an error will be that the solution uses CPM

[maxkatz6]

Does it work well with stable VS and Rider? If anybody have used it already.

[rstm-sf]

If you mean the build and analysis of the code, then everything was fine with me. If you mean the nuget manager, then I can’t say anything

[rstm-sf]

NuGet Central Package Management Comes To JetBrains Rider | The .NET Tools Blog https://blog.jetbrains.com/dotnet/2022/11/07/nuget-central-package-management-comes-to-jetbrains-rider/

[kekekeks]

Note that we'll still be keeping files like https://github.com/AvaloniaUI/Avalonia/blob/master/build/XUnit.props to avoid manually adding 10 dependencies to unit test projects.

[kekekeks]

There are also tricks like this one https://github.com/AvaloniaUI/Avalonia/blob/master/build/System.Drawing.Common.props to make System.Drawing to work properly