Several options in the Features layer were still defined as static fields attributed with ExportOption, which is located in Workspaces.Desktop. Portable MEF does not support static fields for exports so it's necessary to implement IOptionsProviders for each set of options.

Properly specify the round-trip format specifiers for floats and doubles in IMethodXML (used by WinForms)

Add regression tests for #4055

remove error list dead code

Use default OS encoding to decode non-Unicode/non-UTF8 text, if available, instead of unconditionally falling back to cp1252 or Latin1.

Dispose tagger when we're done with it.

Implementation for Analyzer driver v2 for IDE analyzer host

this code belong to old error list. no longer needed.

Use default OS encoding to decode non-Unicode/non-UTF8 text, if available, instead of unconditionally falling back to cp1252 or Latin1.

This brings Roslyn behavior close to VS2013. Fixes #4264. I also believe this change should address #4255, #4222 and #4022.

Changes include:

1. Enhance CompilationWithAnalyzers to allow computing analyzer diagnostics for a specific tree/span within a compilation and/or for a subset of analyzers. Implementation ensures no duplicate analysis by tracking partial analysis state and caching the reported analyzer diagnostics.

2. Overview of the new APIs added to CompilationWithAnalyzers:
    1. GetAnalyzerSyntaxDiagnostics(tree, analyzers, ct)
        1. Analogous to SyntaxTree.GetDiagnostics(ct)
        2. Gets analyzer diagnostics reported by executing syntax tree actions on the given tree.
    2. GetAnalyzerSemanticDiagnostics(semanticModel, spanOpt, analyzers, ct)
        1. Analogous to SemanticModel.GetDiagnostics(spanOpt, ct)
        2. Gets analyzer diagnostics reported by executing rest of the non-compilation actions on the given tree span.
    3. GetAnalyzerCompilationDiagnostics(analyzers, ct)
        1. Gets rest of the analyzer diagnostics which are reported by either of the following means:
            1. Compilation actions (and compilation end actions)
            2. Non-compilation actions reporting diagnostics on different tree: Executing a symbol action on a symbol definition in a tree, can report diagnostic on its partial definition in some other tree.

3. Simplify IDE analyzer driver by switching it to using the new CompilationWithAnalyzers APIs for analyzer diagnostic computation. Both the IDE and compiler drivers now use the compilation event queue model for driving analysis.

Properly specify the round-trip format specifiers for floats and doubles in IMethodXML (used by WinForms)

Fix IMethodXML output for VB array creation expressions with empty initializers

Ignore signature help trigger characters in comments and strings

Properly adjust result type of a user-defined conversion for lifted case.

Handle MemberBindingExpression in Binder.GetEventSymbol

Fix transposed words in file name...

Fix Interactive window indentation

disable loaded dlls checking

it looks like loaded dlls checking action is broken. when it says wrong dlls are loaded, windbg doesn't agree.

Fixes #4028.

The value returned from
```ISmartIndentationService.GetDesiredIndentation``` is absolute, but we
were assuming it was relevant to the prompt.

Fixes #4235

Fixes #4132.

Loosen diagnostics assert

Don't crash when invoking signature help on an inaccessible item.

When gathering symbols for invocation expression signature help, consider the left expression explicitly, not just by name

Add spacing rules around Dictionary Initializers

This reverts the workaround made in fcc26eab. The actual issue was fixed with 0d99437e.

Unblocking the ability to run Unit Tests locally.

This updates the referenced version of 'Microsoft.CodeAnalysis.Test.Resources.Proprietary' from nuget 20150716.7 (20150716.5 and 20150716.6 are also broken) to 20150717.8, which contains the actually signed binary.

Fix customer tests