Package versions not centralized nor up to date

[tannergooding]

I was investigating an issue related to http://source.terrafx.dev/ not staying up to date and it was due to Roslyn being slightly out of date (4.0.0-1.final vs 4.0.0-6.final).

I was going to go and update this but then found that package versions are managed inline for each project, not centrally. This means that not all projects have a "consistent" view of dependencies

Would you take a PR updating PackageReferences to be centrally managed?

• NuGet has https://docs.microsoft.com/en-us/dotnet/core/compatibility/sdk/5.0/directory-packages-props-imported-by-default
• This can also be simulated by Directory.Build.targets and using <PackageReference Update="Name" Version="..." />. The entry in the csproj would then be simply <PackageReference Include="Name" />, leaving it "versionless" (which results in a warning if there is no latter Update entry).

[KirillOsenkov]

sure