Now that the internal dependencies have been removed we can delete the PumpingWait methods.

Support for ISymUnmanagedWriter7 deterministic PDB ID setting

Avoid depencency on the exact order of AssemblyRefs in tests

Add logging to find all reference command handler

Disable BackgroundCompiler on low VM

[AskMode] Rename MS.CA.Scripting.CSharp to MS.CA.CSharp.Scripting...

[AskMode] Allow return statements in scripts...

Fix VSIX based analyzers installed in the extensions hive

Customer scenario: User installs any VSIX based analyzer into their extensions hive, but the analyzers and fixers from the installed extension don't work.

Reason: While making the features layer portable, we changed the analyzer assembly loader for VSIX based analyzers to use the PEReader to get the assembly name for loading the assembly. Prior to that, we used to invoke the desktop API "AssemblyName.GetAssemblyName", which sets the CodeBase property of the returned assembly name to be full path of the assembly. Assembly.Load would attempt to load the ngen'ed image of the assembly, and if it doesn't exist then search will eventually fall back to loading the managed assembly at the CodeBase location. We lost the latter functionality when we made the above change, which causes the assembly loader to fail loading the assembly at the specified full path.

Fix: Move the analyzer assembly loader to the non-portable VS diagnostic analyzer provider service. Any host which needs to support VSIX based analyzers must also implement the assembly loader for VSIX analyzers.

Testing: Verified that assemblies from VSIX based analyzer extensions get loaded successfully and the diagnostics/code fixes work fine. Also added a unit test to verify that host analyzer manager can load assemblies from custom install paths - verified that test fails prior to this change.

Fixes #6285 

...and update namespaces contained therein accordingly.

Remove PumpingWait

This removes PumpingWait from our test infrastructure and replaces it with proper await calls on the Task(s) in question.

Customer scenario: User installs any VSIX based analyzer into their extensions hive, but the analyzers and fixers from the installed extension don't work.

Reason: While making the features layer portable, we changed the analyzer assembly loader for VSIX based analyzers to use the PEReader to get the assembly name for loading the assembly. Prior to that, we used to invoke the desktop API "AssemblyName.GetAssemblyName", which sets the CodeBase property of the returned assembly name to be full path of the assembly. Assembly.Load would attempt to load the ngen'ed image of the assembly, and if it doesn't exist then search will eventually fall back to loading the managed assembly at the CodeBase location. We lost the latter functionality when we made the above change, which causes the assembly loader to fail loading the assembly at the specified full path.

Fix: Move the analyzer assembly loader to the non-portable VS diagnostic analyzer provider service. Any host which needs to support VSIX based analyzers must also implement the assembly loader for VSIX analyzers.

Testing: Verified that assemblies from VSIX based analyzer extensions get loaded successfully and the diagnostics/code fixes work fine. Also added a unit test to verify that host analyzer manager can load assemblies from custom install paths - verified that test fails prior to this change.

Fixes #6285

Add a PE file section for determinism

Fixes for Building with Update 1

Properly map snapshot points up when testing if adornments should be visible or not.

Fixes #5969

By luck, we were getting the real version we did want, but this is
correct.

These interfaces change between VS versions, so this makes us not
dependent upon a specific version of VS.

We don't need SolutionDir or RestorePackages, which were for very old-
style restore systems.

With Visual Studio 2015 Update 1 you should not specify -anycpu
in the runtimes section. Right now we'll have both to allow us to build
with and without Update 1, and we'll remove the old ones once we've
made the transition.

Update 1 also tries deploying implementations for some class libraries,
so I'm updating all our test and VSIX deployment class libraries to
now include implementations.

Update 1 defaults to copying implementations for some class libraries, but we
don't need that for our feature binaries.

Handle in-memory assemblies correctly in ScriptOptions.AddReference and when adding reference to the host object

Handle in-memory assemblies correctly in ScriptOptions.AddReference and when adding reference to the host object

Fixes #6253

Hide namespaces and types of the host assembly

Keep accessor  with attributes on a single line.

Fixes #4720

Don't add accessors for a property with an arrow-body