Fix NullReferenceException's in the result provider when consuming
function pointers.

The VS 2015 Update 1 version of
Microsoft.VisualStudio.Debugger.Metadata.dll adds support for functions
pointers on the metadata api layer.  We represent it in the LMR type
system through new api's to detect if a type is a function pointer and,
if so, get the return type and argument types.  Currently, the result
provider crashes because it doesn't know how to handle a pointer type
with a null element type.  This change adds a couple of checks to
disable expansion on function pointers, which avoids the problem.  With
this change, the EE will simply display the memory address of the
function pointer in the value column, with the function pointer type in
the type column.

To avoid taking a dependency on the Update 1 version of
Microsoft.VisualStudio.Debugger.MetadataReader.dll before it ships, we
temporarily shim Type.IsFunctionPointer() via an extension method.  The
extension method exploits the fact that the function pointer case is the
only time we can have a pointer type with a null element type.  Once
Update 1 ships and the project references are updated, we can remove the
shim layer can just call Type.IsFunctionPointer() directly.

This cleans up Nuget stuff in the Roslyn Code Base.

Fix finding xml help files for winmds in Visual Studio.

* 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)

Offer to add await if converting from Task<T> to T
Fixes #5137

added MS.VB and MS.CSharp as explicit ignored assemblies list for analyzer dependency checker

Add myget buildtools feed to NuGet.config for Microsoft.Build.Mono.Debug

Handle CodeFix with bad ImmutableArray
Fixes #2002

Check IsDefault of any ImmutableArray given for FixableDiagnosticIds, to ensure that it has been properly initialized.
Throw and InvalidOperationException to let the user know to fix their CodeFixer.

Prefer normal files over auto generated files for code generation destinations

guard from null diagnostic

Cleaning up code. Only scripting uses the TryFindXmlDocumentationFile
helper. So moving it to that project and removing code that it doesn't
need.

We should pass the location of the metadata file to the
IVsXmlMemberIndexService than passing the location of the xml help file.
IVsXmlMemberIndexService locates the help file by looking at
appropriate locations such as localized directories or the root
directory where the metadata file is present. This change removes
calling our utility to locate the help file in the VS provider (the helper
is probably meant for internal test applications and such). This fixes a
bug where we were unable to find xml help files for WinMds in the fall
back case where people place help file next to winmds for cultures that
help file wasn't translated for. In such cases, the user should get the
english documentation.

Ensure that IDisposable temps  in a case of dynamic using have "Using" kind.

Using a better name to disambiguate generated files detection vs
generating code which is what the feature itself is doing. Also
asserting that designer files are untouched where expected in tests.

Stop double-reporting Interactive telemetry

Propagate Debugger… attributes from container of async/iterator method to the corresponding state machine type.

```IRoslynTelemetrySetup``` was initialized once by the Roslyn package and
then again by the ```VsInteractiveWindowPackage```, resulting in an
```AggregateLogger``` containing two ```EtwLogger```s and two
```VsTelemetryLogger```s.

Add a generate event test for generating in normal files over auto
generated files.

Don't support compiling scripts with csc/vbc for now...

(Fixes #4360)

Propagate Debugger… attributes from container of async/iterator method to the corresponding state machine type.

Fixes #4521.

Add tests for both VB and C# to verify that generate method picks a
normal file over an autogenerated file when it has a choice. In worst
case where there is no better destination than a autogenerated file, it
is indeed chosen as a valid destination.

These temps have special longlived kind "Using", but were produced as regular temps in the case involving dynamic.

Fixes #5323

In the previous commit, the check for generated files was a bit tight -
The generate method codefix won't even show up if there is not a
destination that is not a generated file. This commit relaxes that
requirement a little bit. It offers the codefix, but "prefers" a
non-generated file over a generated file. If generated file is the only
available destination, then it is chosen.

Add C# language version check for read-only auto-properties.

Disable keyboard shortcut for C# Interactive...

added an internal option to control whether we include custom symbol in bing search query or not

This also disables IDE support for including .csx/.vbx files in a
C# or VB project, and fixes up IVsLanguageBlock service to handle
"incomplete" members (these frequently occur in C# when you parse
global statements in "regular" C# mode).

Update references to DiaSymreader in project.json and proj files

Log Watson events in AppInsights

Remove dnx core warnings