Now that Mac and Linux are using the same version of Mono, we can extend
the Linux support to match that of Mac.

Include accessible private members from outer types in Intellisense

Restores original fix for #2639; avoids re-calculating base types.

Fixes #2639

Bug3092

Add test to prove that encoding is unchanged after tree update

Revert "Remove cross-language assembly checks from typing tests. Re-e…

Revert "Remove cross-language assembly checks from typing tests. Re-enable them for solution load tests."

This reverts commit ae6b19a4.

Remove test intended for stabilization branch only

This change is meant to address crashes like the ones in bug 1140649. The
crashes seem to happen due to exceptions thrown while getting a temporary
output stream to write the PE file to. I have been unable to reproduce
the conditions for the crash themselves -- they only seem to happen on
a Japanese language Windows with a Japanese language copy of Visual Studio.
This fix addresses their symptom by wrapping the CreateInputStream call
during signing with a try/catch and then surfacing the exception as a
diagnostic for signing failure.

We cannot currently add any more localized resources to stabilization, so
this fix is meant to be as targeted as possible and can only deliver
information through existing resource strings.

Handle "Color color" from VB completion

Fixes #3086

the ordering guarantees (deterministic, and for same kind they appear in input order).

Fixes #2909

[Automated] Merge 'stabilization' into 'master'

Add an analyzer to catch incorrect usage of CodeAction.Create API for fixers that support FixAllProvider

Handle non-source file diagnostics in the VB command line diagnostic formatter

User scenario: A CodeFixProvider that supports fix all occurrences code fix, gets FixAll support in IDE if it registers a single code action, but disappears as soon as fixer registers multiple code actions.

Reason: A CodeFixProvider that intends to support fix all occurrences must classify the registered code actions into equivalence classes by assigning it an explicit, non-null equivalence key which is unique across all registered code actions by this fixer. This enables the FixAllProvider to fix all diagnostics in the required scope by applying code actions from this fixer that are in the equivalence class of the trigger code action.
The analyzer added by this change catches violations of this requirement in the code actions registered by a CodeFixProvider that supports FixAllProvider.

Fixes #2864

Ensure SemanticModel reports node as a default instance access rather than as a type reference, when the type reference is reclassified as such.

User scenario: User compiles a project with analyzers, and analyzer(s) generates a diagnostic with location in a non-source additional text file, but msbuild doesn't report such analyzer diagnostics and exits with code 1 with no output.

Bug description: For analyzer diagnostics in additional file, VB command line compiler doesn’t output any file information or squiggles. However, it does include the file name and location in the output. This format doesn't match the Vbc MSBuild task parsing logic which expects the output to have either all of this information (file path, location, file content and squiggles) OR none of it for no-location diagnostic. This causes the Vbc task to ignore additional file diagnostics.

Fix description: Fix the VB command line diagnostic formatter to always output diagnostics in either of the above 2 formats expected by MSBuild. For additional file diagnostics, the formatter now attempts to read the additional file stream and if it succeeds, formats it as a source diagnostic with location info and squiggles. Otherwise, it formats it as a no-location project diagnostic.

Testing: Added regression test + existing tests. Also verified that the original issue reported on Roslyn.sln is also fixed by this change.

Clean up EE skipped tests

fixed a race where build only errors are not cleared correctly

fixed a race where build only errors are not cleared correctly

Unskip the ones associated with closed bugs and make sure the others are
clearly labelled.

Fixes #3086.

Rename dashboard navigation tweaks

Add an analyzer that detects incorrect action registrations for stateful analyzers.
Fixes #2949 

Fixes #2949

User scenario: User writes an analyzer that either defines a CompilationStartAction or CodeBlockStartAction to perform stateful analysis on the compilation/code block.
An analyzer start action enables performing stateful analysis over a given code unit, such as a code block, compilation, etc. Careful design is necessary to achieve efficient analyzer execution without memory leaks. This analyzer provides the following guidelines for writing such analyzers:
1. Define a new scope for the registered start action, possibly with a private nested type for analyzing each code unit.
2. If required, define and initialize state in the start action.
3. Register at least one non-end action that refers to this state in the start action. If no such action is necessary, consider replacing the start action with a non-start action. For example, a CodeBlockStartAction with no registered actions or only a registered CodeBlockEndAction should be replaced with a CodeBlockAction.
4. If required, register an end action to report diagnostics based on the final state.

Fix description: We already have an analyzer flagging RegisterXXXAction invocations for other incorrect usages. This change adds 2 more rules to this analyzer to flag:
1. Start analysis context objects with only a registered end action.
2. Start analysis context objects with no registered actions.

Testing: Added unit tests for this analyzer + manual testing. Verified existing tests pass.

cleanup some code

renamed id to Id to match other variable names. and added readonly.

changed bing search to use bing dev search