This should either be defined globally or not at all.  Repeating all the logic on a local level is just wasted time.

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.

This change drops support for .NET 4.5 and retargets to desktop
4.6 + CoreCLR. It also fixes up various analyzer warnings that
were created due to the move.

Fixes #12926

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.

We need to consume the VSSDK nugets for these assemblies in order to
build/run on a machine without VS 2015.

This reverts commit 7debfc47.

by removing `<DebugType>` lines from projects that import `VSL.Settings.targets`

* This updates all references to nuget.exe to use the copy in the root.
* This deletes all NuGet.config and NuGet.exe files that are not in the root.
* This removes all references to NuGet.targets (which is obsolete and no longer exists)

This moves all of the InternalsVisibleTo which were defined in code into
the project files where the majority of the IVT definitions lived.

The targets files were previously split into an open version in
Microsoft.CodeAnalysis.Toolset.Open and a closed version in build/. This
unifies the four targets into two new targets, VSL.Settings.targets and
VSL.Imports.targets, and moves all the targets from ..Toolset.Open into
the build/ folder.

Update versions of Microsoft.DiaSymReader and Microsoft.NetFX20 packages to release 1.0.5 and1.0.3, respectively

This is the second of a sequence of changes.  (The first was 3dd1f2bf.)  In
this change we start returning custom type info (effectively just the
flags of DynamicAttribute packed into a byte array) from calls to the
expression compiler so that they can be consumed by the result provider.

TODO: The API for locals is still in flux and we don't presently have a
place to return the custom type info.

TODO: This change does not associate custom type info with locals declared
in the Immediate window.

Upgrades System.Collections.Immutable to 1.1.34-rc and
System.Reflection.Metadata to 1.0.19-rc.

Since hoisted locals are fields, they are in scope throughout the entire
method body.  However, from the user's perspective, they are still locals,
so we attempt to retain their original scopes during debugging.
Unfortunately, C# and VB use different mechanisms for doing so.  In order
to make the code more consistent, and to simplify consumption of the new
PDB format (which is more similar to C#), we introduce an abstract type
InScopeHoistedLocals that represents the set of in-scope hoisted locals in
a consistent way in both languages (and both PDB formats).

1. Compile them against Profile7.
   a. Swap out a few APIs (e.g. using GetTypeInfo for reflection).
   b. Introduce an abstraction layer so that we don't have to instantiate
   DkmDataItem (caused a VerificationException).
   c. Include WindowsProxy.winmd as an EmbeddedResource directly, rather
   than through a resx file.
2. Swap the output locations of the ResultProvider projects: Portable goes
to the main output directory and NetFX20 goes to a subdirectory (NetFX20).
3. Include the Portable ResultProvider assemblies in the EE vsix, rather
than the NetFX20 ones.

Rebased from https://github.com/tmat/roslyn/tree/DiaSymReader