Fix handling of abstract/virtual in structs

Don't parse out a local declaration where there clearly isn't one.

Fixes: #4014

Remove BuildTask ref from VS Setup project

If we see:

```c#
  Identifier1
  Identifier2();
```

Don't parse that out as a declaration of a local called "Identifier2".

Migrate C# tests to be less sensitive to the precise text of error messages

Merge current update-1 branch contents to master

Add missing ERRID to HasDuplicateTypesOrAssemblies...

Duplicate references between weak named assemblies have a different error code in VB.

Added a link to the Wiki on here.

Replace loop with SelectMany call

Add import can now add project references.

Upgrade NuGet to 3.3.0.212.

Show additional pieces of information in the preview changes dialog to make it clearer about what change will actually be happening.

Temporarily disable warning until we get an AnyCPU MSBuild NuGet ref

add pretty listing support for integer literal tokens

Addressing documentation feedback

Organize 'Go To Adjacent Member' unit tests and share code between C# and VB

MSBuild is unhappy that we're building the build task as AnyCPU because the
MSBuild core task reference is x86. The proper fix is for the MSBuild Core task
to also be compiled as AnyCPU, but until we can get an updated task this should
suffice. See issue #6986.

Implement View.SynchronizeClassView command

Thanks @diryboy for catching the typo.

Fix code formatting.

NuGet has now resolved #6981 which caused
us to roll-back to 3.2 last time we upgraded
to 3.3.