Use central package management and update all references

[satano]

Changes in this PR:

• Set up some code style in .editorconfig.
• Consolidate all references into Directory.Packages.props.

Fixing tests

After switching to .NET Framework 4.7.2, MigrationToolVersionInfoTests were failing. It seems, that in this framework when running tests inside Visual Studio. The problem was in MigrationToolVersionInfo constructor, where Assembly.GetEntryAssembly() returned null and so FileVersionInfo.GetVersionInfo throwed an exception. The problem was, that FakeMigrationToolVersionInfo inherited from MigrationToolVersionInfo and so that constructor was automatically called. I believe, this logic is not needed in fake class, so I removed inheritance and implemented just the interface.

[CLAassistant]

All committers have signed the CLA.

[MrHinsh]

This one will take a little longer to review as 8.0 was introduced deliberately.

We are moving to 8.0 for all projects, and some dual build both an 8.0 and 4.7.2 output. As many projects that can use 8 should use 8, and dual build for dependancys.

A pending task for me is to merge MigrationTools.ConsoleFull and MigrationTools.ConsoleCore into a single entry that builds both 8.0 and 4.7.2!

[MrHinsh]

Everything else apart from the TargetFramework changes are good...

Would it be better to move everything to <TargetFrameworks>net472;net8.0</TargetFrameworks> except MigrationTools.Clients.TfsObjectModel and MigrationTools.Clients.TfsObjectModel.Tests as they depend on the TFS Object Model which is net472 only.

[MrHinsh]

This is a .NET Core app and must be built in 8.0

[MrHinsh]

This should be 8.0

[MrHinsh]

The netstandard2.0 projects are shared between the net8.0 and net472... there is probably a better way to use <TargetFrameworks>net472;net8.0</TargetFrameworks> instead

[MrHinsh]

Create a branch for the change before (Use .NET Framework 4.7.2 for almost all projects its likely that the build will succeed... and we can get those awesome changes incorporated.

[satano]

Added two more commits:

• Return back .NET 8.0 for projects.
• Updated some more references with high severity vulnerabities.

[satano]

I one before the las commit a47eb7a some tests failed. So I reverted back the project files (instead of netstandard i used net472), but the build checks did not finished yet. It has beet 20 our so far. Does it really takes such a long time, or is there some problem?

The other thing is, that I have a "works on my machine" problem. Because I always run tests and all of them pass. But some of them faile in CI pipeline.

[MrHinsh]

@satano I need to approve external build runs...

[MrHinsh]

https://github.com/nkdAgility/azure-devops-migration-tools/actions/runs/11859873660?pr=2508

[satano]

Well. I do not know why some tests are failing on CI build, so I returned back netstandard2.0 and all pacakge versions (so packages are not updated). The only thing is, that the project uses centra package management for better handling references and unneeded direct references are removed. Hope it will pass.

[satano]

OK. Last attempt. I reverted everything (even using of non-needed dependencies), just used central package management.

[satano]

main branch has changed, so I rebased this one.

[MrHinsh]

OK. Last attempt. I reverted everything (even using of non-needed dependencies), just used central package management.

Its always a good idea to have separate discreet changes :) ! This codebase is quite complex and has a number of quirks.