Removing the last packages.config and replacing them with project.json

Instrument the body of an expression-bodied lambda for dynamic analysis

Fixes #12940
Fixes #14110
Fixes #15640

Do not mark argument values as bad due to issues with names.

Check for assembly resolution errors in bootstrap build

VisualBasic function breakpoint binding

add PrimaryWorkspace concept in OOP

Handle additional cases in MemberSemanticModel.GetQueryEnclosingBinder

Our current setup for .Net Core requires us to do manual assembly redirection in our MSBuild Task.  The setup has no
good way to detect at compile time when our source code and NuGet references get out of date.  This change allows us
to at least detect at bootstrap time.

The problem is demonstrated by the following test case:

```
struct S { public int X, Y; }

class C
{
    public static void Main()
    {
        S s;
        s.X = 5;
        void Local()
        {
          s.Y = 10;
          System.Console.WriteLine(s);
        }
        Local(); // error CS0165: Use of unassigned local variable 's'
    }
}
```

Definite assignment should allow structs to be assigned piecewise
through a local function. The problem is that printing `s` is normally
regarded as a use of `s`, not its constituent fields. This causes the
analysis to effectively lose information about s.Y being assigned.

The fix is, when recording captured reads of possibly unassigned
structs in a local function, recursively record the possibly unassigned
constituent fields, rather than the struct variable.

Fixes #14097

Add System.Xml.ReaderWriter.dll to compilers vsix

Fix race condition writing assembly attribute file

Fixes #15732.

MSBuild generates the TargetFrameworkAttribute file to the same path on
disk for equivalent combinations of TargetFrameworkIdentifier and
TargetProfile.  This means if two projects in a solution have equivalent
identifiers, their builds will race to write the same file to disk.

This is safe by virtue that the content of the file is the same in both
cases.  Hence it doesn't really matter who wins the race, both projects
see the same output.

This is frustrating though because even though it's safe, MSBuild still
isssue a warning when it happens.  This breaks our desire to have
warning free builds.

To fix this we will instead generate the file to the Obj\ProjectName
directory.  This means every project gets their own indepnedent copy of
the file, eliminating the race.

closes #10116

Add System.Runtime.InteropServices.RuntimeInformation to common nuget…

Merge dev15-rc2 into master

Adds Prerequisites to vsixmanifest templates

Adjust scope of variables declared within a ‘for’ condition and ‘for’ incrementors.

Don't manually construct strings.  It doesn't work for localization.

Variables declared within a ‘for’ condition are in scope only inside the condition, incrementors and body of the loop.
Variables declared within ‘for’ incrementors are in scope only inside the incrementors.

Related to #15630.

Remove call to SetProgress for performance reasons.