# Conflicts:
#	src/EditorFeatures/CSharpTest/Diagnostics/GenerateMethod/GenerateMethodTests.cs

…to interpolated string

… fake SymbolAnalysisContext

…rticular provider

Fixes dotnet#24112

…wing an exception

…kalloc expressions (dotnet#26248)

* Produce correct diagnostics on implicit operator conversions for stackalloc expressions

* PR Comments

Naming style for locals

Fix the message for Make Field Readonly

…n-interpolated-string-refactoring

Escape curly braces in string literals when converting concatenation to interpolated string

Use appropriate analyzer category for these analyzers.

Fixes dotnet#25829

)

`IAssemblySymbol.GivesAccessTo` now has a shared core implementation that permits operation across IAssemblySymbol implementations.
Fixes dotnet#26459
Fixes dotnet#26723
One remaining difference is in the treatment of a strong named assembly and a weak named assembly.  C# treats them as being (capable of being) related for error recovery.  VB does not. We would like to strengthen C# but that may be a breaking change, so we're leaving it as is, at least for now. (See also dotnet#26722)

….8-preview1

Merge dev15.7.x to dev15.8-preview1

Exclude System.Net.Http from PortableFacades

…ertionText

Use completion item InsertionText in the debugger, even before any non-debugger completion sessions have run

"Generate method" refactoring enabled if method name is equal to imported type.

The data is pointing towards procdump being the cause of our random AVs
during the Spanish runs. Disabling procdump on the Spanish runs as an
experiment to see if it increases stability here.

Disable procdump on Spanish runs

Simplify our use of an extension.

…dev15.8-preview1-to-master

…o-master

Merge dev15.8-preview1 to master

…Json