* Copy escape scope of pattern locals from source expressions

* Document breaking change

* Reporting errors on foreach ref/readonly declarations in async/iterator methods

* PR Comments

* ToBadExpression() checking incorrect HasAnyErrors API

* Undo fix for 15.8

* Fix build break

Make ShadowCopyAnalyzerAssemblyLoader threadsafe

* workaround on long pending incremental parsing requests

* use GetSyntaxTreeAsync so that underlying AsyncLazy reuse same Task for parsing when there are multiple requests

* comment updated

* more comments

Fixes #20169

Trap all exceptions from the IVsFileChange service

Merge dev15.8-preview3 to master

Add an async test case for a try/finally with an uncaught exception

Previously we only trapped some exceptions from the VS file change
service, letting the rest propagate. It turns out this doesn't work
terribly well: if there is an exception, the Lazy<> we did the
subscription with will still hold onto the exception, any use of the
Lazy then rethrows. This means StopFileChangeListening/Dispose never
actually clear the underlying cookie, and we crash in our Finalizer
assert later.

Raise events when connecting or disconnecting from a workspace for semantic changed

Fix for #2128 (Outlining cuts off closing } )

Fix #26358: AbstractDocumentationCommentCommandHandler has hardcoded Windows line ending

Adding a backwards compatbile constructor to ContainedLanguage for Tyepscript

Removed text truncation logic from Introduce Variable codeaction

Avoid toggle checkbox when clicked on an option's description.

Multiple callers on multiple threads risked potentially overwriting the
same files or having a mismatched Mutex which could have resulted
in things being deleted underneath us. This is now properly safe.

There are two consumers of this type today: Visual Studio, which was
currently calling this on the same thread the whole time (but that's
changing) and VBCSCompiler, where it's a singleton and thus this might
have been broken all along.

Updated unit test to test just inserted code, to work around unit test infrastructure  assumption that all code is `\r\n`

I used `\n` and `\r\n` in string instead `@""` because as far as I understand on Windows/CI code is checked out with `git config core.autocrlf` which means it modifies line endings...

Update "use 'is null'" analyzer to also find and offer to simplify "(object)expr == null".

Merge dev15.8-preview3 to master

Merge dev15.8-preview3 to master

* Orchestrated build dependency uptake

* Remove duplicate NuGetPackageRoot definition

This bug ocurred because the height was calculated too early. We can't rely on `view.LineHeight` too early because Visual Studio may still change it depending on your `Font Settings` or `Editor Zoom %`.

I've also done some refactoring & removed the comments because they are no longer needed.

Report conflicts when renaming a partial method definition's parameters

* Validate full path of file instead of file name in parsing /resource args

* PR Comments

* Fix build break

 Strip common prefixes before applying naming suggestions

Fixed incorrect suggestion for object initialization simplification

Exclude nested captures from quick-info

Updated dev15.8-preview3-vs-deps channel

Fix unnecessary cast