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.

Fixes #3096.

Dont fail format on MAS with Tabs on

Format during Return in a Brace Completion Session

Unflip condition in InteractiveWindow.InsertCode

Never show the enum backing field in the completion list

Refactoring for readability

Refactoring - Introducing a local

It should work when there is no standard input.  This was causing problems
for a lot of (still skipped) integration tests.

change variable name for better understanding

Add a test for #4136

Don't trigger "completionlist tag" completion in trivia

Fix #3447 Format should happen when Return is issued after starting a
Brace Completion session. We should not listen to
FeatureOnOffOptions.AutoFormattingOnCloseBrace when 'Return' is pressed
during the Brace Completion session

Fixes #3518.

Conflicts:
	src/EditorFeatures/VisualBasicTest/Completion/CompletionProviders/CompletionListTagCompletionProviderTests.vb

Shared IntelliSense should treat fields and properties with the same …

Use different ContentType for InteractiveWindowCommands...

Support EnC for string interpolation

- Fix #2556 and internal bug 1198941

Fixes #4019 While formatting a complextrivia that falls as a end_of_tree
trivia of a tree that is being formatted, adjust the span of the
ComplexTrivia for formatting purposes

Fixing Build/AssemblyVersion during OfficialBuild

Unskip test blocked by #2721.

Allow top-level extension methods in VB script code

I didn't know about PredefinedInteractiveCommandsContentTypes
when I initially added the ContentType attribute to the interactive
commands.  Switching to use the constant defined there (instead of
just "code")...

This fixes the Build/AssemblyVersion to be the same as RoslynSemanticVersion when OfficialBuild is true, but no BuildVersion was passed in.

Move binding redirects for InteractiveWindow...

...to the InteractiveWindow VSIX.  This allows the rest of the Roslyn
components in Roslyn.VisualStudio.Setup to move to version 2.0.0.0 while
leaving "NewVersion" for the InteractiveWindow components at 1.1.0.0.

Fix bug 4090

Renaming Interactive product assemblies...

"Roslyn" -> "Microsoft" or "Microsoft.CodeAnalysis"

We should only do the color color binding check of the expression originally bound as something other than a type or namespace.

Remove namespaces from ScriptOptions.Default

Removed explict references to System.Collections facade

Include content files in Roslyn.VisualStudio.Setup.Interactive.vsix

Opt projects building against portable into the portable flavor.

Specifically, the default response files for initializing the Interactive
windows.

Fixes #4203