Understanding dependencies and supported scenarios

[jaredpar]

There are a few dependencies in this project that are quite old. For example the Microsoft.Build is referenced at 16.8 in Common.csproj. That is a several years old version and does not correspond with an LTS release of Visual Studio (the 16.11 would). A few other packages like Microsoft.CodeAnalysis are similarly out of date.

I was considering sending a PR that updated them but first I wanted to make sure I understood all the scenarios here. The tool itself seems self contained and exe driven so I can't forsee moving to new versions being an issue here. But I wanted to check and make sure I wasn't missing any scenarios here where limiting to older versions of packages may be important.

[KirillOsenkov]

It’s OK to bump everything, I just never had the time.