* Remove RuntimeIdentifier specification

* Arcade directory layout

Implicit framework references were disabled at the time we moved over to
the new SDK due to some remanants of project.json in our build. Those
have all been cleaned up now and hence moving us over to using implicit
framework references.

Not having this enabled meant the API surface we were targeting in our
projects was not actually what was available in the project target
framework. Instead it was the intersection of the target framework and
the set of NuGet packages we reference. This meant that code which
should work simply wasn't due to the API surface not being correct.

Many of our VB projects today rely on having an empty default namespace
and explicitly specifying the full namespace in source. In the new SDK /
dir props world this can only be done by explicitly marking the
namespace as empty in the project file. Can't do the centralized control
that we do today.

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

The warning B40057 used to be suppressed at a global level in PCL /
Desktop projects. The SDK does not suppress this warning and hence
converting to the new SDK caused this to show up.

Previously a number of developers fixed this problem individually. The
correct solution is to suppress it globally as was done previously.

At this point the Concord project exists just to fix a signing issue in
the Debugger NuGet packages.

This project is causing problems in our port to the new SDK because it's
a Net 45 portable project that is referenced by Net 20 projects.  The
old build silently ignores this incompatibility but the new SDK takes
issue with it, and the method it uses to pass DLLs around.

Taking the simpler approach here of just fixing the signing issues (side
thread going with debugger team) and removing the project.

The motivation for this change is to simplify our build and develop
steps.

Previously our compiler builds included files generated into the Obj
folder during previous phases of the build.  This meant that in order to
open Roslyn.sln successfully the code needed to be built first.  Not
ideal.

The generated code involved is rarely changed.  But in order to build
the generators themselves must be built and run as a part of every
build.  This is doable but adds unncessary overhead to development and
complicates our build files a bit.

This approach checks in the generated files which should have the
following benefits:

- Roslyn.sln can be open after a restore
- Build process is simplified and marginally faster for many operations
- Generated code now participates in GitLink

The VsdConfig.targets file was not located in our core targets location.
Moving there as this is the appropriate place for all targets / props
files in our build.

Additionally changed it to use the vsdconfig from our NuGet packages
directory instead of hard coding Visual Studio.

The VsdConfig.targets file was not located in our core targets location.
Moving there as this is the appropriate place for all targets / props
files in our build.

Additionally changed it to use the vsdconfig from our NuGet packages
directory instead of hard coding Visual Studio.

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

This setting controls binary deployment hence it needs to be centrally
managed to help ensure we have a correct build.  Custom projects can
continue to control this setting themselves.

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.

The ImportGroup element is just noise.  It was also used very inconsistently in the repo and often within the same project file.  Just remove it.

This change reverts the part of #12497 that removed Concord.csproj.  This
project will now be used to express the nuget dependency on MS.VS.D.Engine
and MS.VS.D.Metadata as well as deploy the portable version for testing
(and, as the title states, set the OSS sign bit post-build).

Also, move to the latest version of the 14.3 Concord nugets (which allows
us to remove explicit <Reference> items in our portable projects).

This reverts commit f88047f5, reversing
changes made to b9438f7c.

Several of our EE binaries needed to be signed with different certificates than the standard Microsoft one.  Functionality was added to specify the certificate for the binary in question and all remaining references to the AuthenticodeCertificateName property were removed.

Several of our EE binaries needed to be signed with different certificates than the standard Microsoft one.  Functionality was added to specify the certificate for the binary in question and all remaining references to the AuthenticodeCertificateName property were removed.