Work around dotnet#1675 for C++ Code Analysis scenarios (dotnet#1699)

This addresses the repro case for dotnet#1675, but not its root cause. By
providing a `codeBase` for the CA assemblies, we ensure that any running
MSBuild can find them when deserializing a log message.

Respect projects that say they only have one TFM (dotnet#1667)

Partially fixes dotnet/sdk#739.

The first iteration of cross-targeting support code unconditionally
queried each ProjectReference for the best TFM to build against, and
then explicitly specified that TFM when building the reference. This
caused a race condition when building a set of projects that had a
single-TFM project and another project that had a reference to it. The
entry point (probably .sln) build would build the referenced project
with no TF specified, and then the referencing project would build it
with an explicit TF specified. These two builds appeared different to
the MSBuild engine (because they had different sets of global
properties) and so were both executed, resulting in a race condition.

The fix is in two parts:
* Allow a project to report back through GetTargetFrameworkProperties
that it only has one TF to build.
* When a project reports that it has only one TF to build, issue its
build request without specifying any TF.

This commit is the latter.

Include implicit imports in GetLogicalProject() (dotnet#1571)

Closes dotnet#1570

Added link to up for grabs issues, small formatting changes, cruft re…

…moval

Merge pull request dotnet#1446 from rainersigwald/ignore-implicit-on-…

…remove

Ignore implicit on remove

The Full Framework MSBuild inserted into Visual Studio 2017 RC.

The .NET Core MSBuild delivered with dotnet CLI 1.0.0-preview3-004056.

Only record extra Evaluator data when needed (dotnet#1060)

This saves memory

Make MS.Build InternalsVisibleTo MS.Build.Conversion.Core

Previous versions have shipped with InternalsVisibleTo set for the
Conversion.Core assembly. OSS version has never had that set which
causes some issues. For example, crashes trying to use the
ErrorUtilities VerifyThrow functionality which is all internal.

This tag corresponds to the version of MSBuild packaged with Visual S…

…tudio 2015 Update 3. The actual sources for that release are an internal repo at a state that corresponds to this commit.