Adjust an assert condition in BindForEachPartsWorker.

PERF: Reduce allocation in PatternMatcher constructor

Implement support for EnC of constructors and member initializers containing lambdas

Update Edit and Continue analyzers to use resource strings

Change workspace output pane to IntelliSense

Do not require an assembly-level ExtensionAttribute...

Generate types with the correct accessibility if they are part of public...

Merge branch 'GenerateTypeAccessibility' of github.com:jmarolf/roslyn into GenerateTypeAccessibility

Conflicts:
	src/EditorFeatures/VisualBasicTest/Diagnostics/GenerateType/GenerateTypeTests.vb

fixes internal issue #1107929

update comment banner matchers to not require a trailing newline

Fixes #1733.

Update AnalyzerFileReference.DisplayName

Don't show the file extension for in the `DisplayName` for
`AnalyzerFileReference`.

fixes internal issue #1107929

Introduce new entry named 'Default' in solution explorer context menu

Fixes #1512 

in order for the C# compiler to recognize extension methods
contained within the assembly. In other words, we assume every
PE assembly may contain extension methods.
Fixes #365

Offer to generate static class in Imports statement

Add global undo to ContainedLanguageCodeSupport.TryRenameElement

Add "Brace Matching" color

check a symbol for null before descending into its base type

Fixes #1512

The solution explorer context menu that allows users to change severity of analyzer-reported diagnostics currently displays the following entries -
    Error
    Warning
    Info
    Hidden
    None

When the context menu is displayed, a check mark is displayed next to the entry representing the severity of diagnostic as configured in the project's ruleset file. This works fine in cases where a severity is explicitly specified for the diagnostic in the ruleset file.

However, in cases where the severity is not explicitly specified in the ruleset file, the diagnostic is assigned its 'default' severity and we don't display a check mark against any entry in the above menu. As noted in #1512, this is confusing because the 'default' severity is also one of the severities listed above.

This change introduces an additional entry named 'Default' in the above menu that will be checked in cases where the dagnostic does not have an explicitly specified severity in the ruleset file. If the user clicks this entry to change the severity of some diagnostic to 'Default', the entry corresponding to this diagnostic is removed from the ruleset file.

Clean up `AnalyzerReference` and derived types.

I'm doing a lot of other work that uses the `AnalyzerReference` type and its derived types, and the API could stand some clean up and simplification. This includes the following changes/refactorings:

1. Remove `AnalyzerReference.IsUnresolved`.
2. Push `AnalyzerFileReference` down into the CodeAnalysis (Portable) project.
3. Add an `AnalyzerReference.Id` property.
4. Update `AnalyzerFileReference` to take an `IAnalyzerAssemblyLoader` rather than a `Func<string, Assembly>`.

Please see the individual commits for more information.

start of a file

Avoid exceptions for rename conflicts with implicit names

Display Aliases (e.g. $exception) in the Locals window

Add missing On keyword to Option statements

Move aliases out of ```EvaluationContext``` so that they don't interfere with our caching strategy.

Clean up the overall diff.

Populate the new DkmClrLocalVariableInfo.FullName property.

Note: FullName is the expression used for Add Watch and will generally be
the local's name, whereas Name is the string displayed in the Locals
window and may be a prose description of the local (i.e. not the local's
name).

1) Instead of asking for the type of an individual alias to determine if
it exists in the current context, ask for a list of all aliases up front.

2) Include aliases in the result of CompileGetLocals (so that the debugger
no longer has to partially populate the window).

Bonus: Fixes #878.