…etry

…r compatibility

…vicehub analyzer

…dev/shech/CheckConfigurationCapability

…ionCapability

[17.6] Only send workspace/configuration request when client supports that

EnC telemetry improvements

…match (dotnet#66992)

* Add tests

* Check count before reusing batched items

* Add missing assert

* Fix local function name casing

* Fix notation in comment

* Revert "Check count before reusing batched items"

This reverts commit 2984b5f.

* Check state table counts before caching

* Clarify doc comment

* Add a test

Co-authored-by: Chris Sienkiewicz <[email protected]>

* Compute `IsCached` flag only in the builder

---------

Co-authored-by: Chris Sienkiewicz <[email protected]>

* Use exception with specific type and HResult to aid tracking in telemetry

* Associate rude edits with project id

…ptionsChange

Add RequiresNonDocumentChangesTag to ProjectOptionsChangeAction

…med-types and methods. (dotnet#68131)

* Use a singleton for empty type-parameters for named types

* move type parameters down

* Optimize methods as well

* Always create indirection

* Move type

* Apply suggestions from code review

* speeling

* nrt

* Inline

* Simplify

* Change to abstract override

* Record added node output states as new

The `(EntryState.Modified, EntryState.Added) => IncrementalStepRunReason.Modified` state mapping was recently added in dotnet#61308, but doesn't look correct to me. Since this value is used as the output status, and the outputs are new, I believe the correct state should be `IncrementalStepRunReason.New` instead.

* Update tests that were added since I originally implemented the change

* Update documentation for IncrementalStepRunReason

* Update VB tests also

* Add note about breaking changes with IncrementalStepRunReason

---------

Co-authored-by: Jan Jones <[email protected]>

* Add a test

* Display standalone parameter names by default

* Document breaking change

* Update tests

…-main