In the new SDK we no longer have a need for ProjectGuid. This change
will:

- Remove ProjectGuid from project files
- Remove Name + Project items from ProjectReference entries
- Change BuildBoss to enforce both of these items

Migrated the remainder of our code base to use the new SDK via the
ConvertPackageRef tool.

https://github.com/jaredpar/ConvertPackageRef

we found 2 issues. 1. hard to validate persisted data and 2. recalculating checksum is faster than reading from storage.

This is an automated migration of our project files to the new SDK /
PackageReference.  It is done using the tool located here:

https://github.com/jaredpar/ConvertPackageRef

We either don't use these, or pull them in from NuGet.

This project is no longer necessary.  It used to help us get TDD working fine in Visual Studio.  That's no lonegr needed with the recent build cleanup.  TDD still functions with this project removed.

Ensure that all *.*proj, *.props, and *.targets files are prefixed with the xml and copyright elements

latest version of JsonRpc supports custom JsonConverter which I added for these 4 types. Checksum, SolutionId, ProjectId, DocumentId

we can add more to AggregateJsonConverter for common roslyn types.

unit test added

The dependency projects were added as a way to help unify our project.json references.  Instead of every project referencing the NuGet package, we had a dependency project which referenced it and everyone referenced that dependency project.  Due to the transitive nature of NuGet it would be roughly equivalent.

This system had a number of downsides:

1. There was no enforcement.  Even though dependency projects existed, there was no mechanism to force developers to use them.
2. Getting the granularity correct was tricky.
3. The projects themselves have special props / targets to get them to produce no output.  This can trip up MSBuild up to date checks.

Since then though we've begun using RepoUtil to verify our NuGet reference correctness.  This removed the need for these projects and hence I'm removing them from our build.

TLDR: artifacts are going to move around in Binaries\Debug and the directory is going to get a lot bigger.

At a high level build projects can be classified into three categories based on how they write output:

- incorrect: a given output path is written to more than once with different contents
- less correct: a given output path is written to more than once but always with the same content
- correct: a given output path is written to exactly once

Today the roslyn build is decidedly “incorrect” as pretty much every file is written directly into Binaries\Debug. This means it ends up writing pretty much every Visual Studio SDK DLL twice: once for Dev14 and once for Dev15. For example at various points in the build Binaries\Debug\Microsoft.VisualStudio.Text.Data.dll may refer to Dev14 and at others it’s Dev15. If this seems like a scary proposition for a build that’s because it is indeed scary and it has real consequences. By now pretty much everyone on the team has hit the build race condition that is dragging down our PRs.

The general fix here is to move build outputs into separate directories. Instead of building to $(Configuration) projects now build into say $(Configuration)\Exes\$(MSBuildProjectFileName). This will have a substantial increase in the size of Binaries. We will be looking into ways to reduce that. In the short term though build stability far outweighs the size increase.

This change takes us most of the way to "correct". There are several places I had to compromise in order to get this initial change in:

- UnitTests still build to a common output folder (one for Dev14, another for Dev15). Pulling unit tests apart is going to take a bit of work.
- Every project has a <RoslynProjectType> entry. This will go away in the future for most projects. It's temporarily needed so I can fix roslyn-internal in parallel without taking down the build.
- VSL.Imports.targets is messy. Unavoidable for now due to the above. It will get cleaner as I iterate on this.

None of these are relevant to the underlying race condition. Hence it's okay to push them off.

following up unit tests will add more tests and add proper listener to remove explicit delay