turn off csharp full solution analysis.

fixed live diagnostic argId leak

it looks like my previous update 2 leak fix for Task introduced argId leaks. since this was much smaller leak than before I didn't notice it being leaked.

to support this, I added a way to set different default value per language

Do not throw if initialized by Winforms UI thread
Fixes https://github.com/dotnet/roslyn/issues/10510

Simplest fix for this issue to be considered for Micro-Update

Prepare cibuild.cmd (stabilization branch) to receive /buildTimeLimit

Enc: async/iterator editing regression fix

explicitly dump entire XML fragments to help with debugging

Fix a race in the production of compilation events.

Fixes #9759

Report NoPIA EnC errors after all indices have been created

[Stabilization, Crash] Fix crash when NavBar navigating to symbols without source locations

Fix SHAs in project.lock.json files

Check if syntax tree is present

Fixes internal bug 187905

In a Visual Basic WinForms application, the Application.Designer.vb file
contains one Partial of the MyApplication class. Using the NavBar in
this class to attempt navigation to “Main” crashes VS. This crash will
happen any time a non-source symbol (that’s also not a “code generation”
entry like “New” and “Finalize”) finds its way into the NavBar, but this
is the only example I currently have.

This has been broken since Visual Studio 2015 RTM, but previous versions
of Visual Studio showed a "The definition of the object is hidden."
dialog in this case.

Fix crash in Inline Rename

As the types into an Inline Rename field, the Rename engine attempts to resolve conflicts at each reference. It does this by expanding nodes are the references and then simplifying them down to the smallest node that does not change semantics.

During this process, one of the expansion steps is to add explicit types to lambda parameters that were defined without types. However, the expander wasn't rewriting lambdas with multiple parameters correctly. Essentially, the rewriter assumed that, when replacing a node within a `SeparatedSyntaxList<T>`, the identities of other nodes within the list would not change. However, that's not the case. So, it would successfully replace the first parameter within a lambda's parameter list. However, when it attempted to replace the second parameter, the *original* second parameter could no longer be found in the `SeparatedSyntaxList<T>` because the identity of the second parameter in the list had changed. At this point, `SepratedSyntaxList<T>.Replace(...)` would throw an `ArgumentOutOfRangeException` and VS would crash.

The user scenario is that typing within an Inline Rename field can cause Visual Studio to simply crash, resulting in potenal data loss.

The fix changes the rewriter to not pass the original parameters to `SeparatedSyntaxList<T>.Replace(...)`. Instead, it passes the parameters that are contained when the new list as it builds it up.

This is a regression introduced after Update 1 with PR #6432.

Update System.Reflection.Metadata to 1.2.0 release

[Stabilization, Crash] Rename: Don't restrict rename project search set for explicit interface implementations

Fix null ref in C# expander when adding cast to lambda return statement

[Stabilization] Codefix ordering: Prevent Low Priority fixes from interfering with Medium Priority fix ordering

Put the 'Add Nuget Reference' feature behind a disabled regkey option.

Explicitly list dependencies in TestUtilities project.json, the new nuget.exe doesn't flow them anymore.

Fix intermittent crash in CompilationWithAnalyzers due to an OjbectDi…

Fixes #8139

We were previously asserting that renaming a private member meant that the rename operation would occur entirely in that member's declaring project, but rename affect other projects if the private member is an explicit implementation of a public interface member.