- backport of #36898

Don't clear NuGet caches at all (#36898)

  - `$use_global_nuget_cache` and `$useGlobalNuGetCache` have default values in our pipelines
  - therefore, cache is always within `$(System.DefaultWorkingDirectory)` and should not exist at job start

- backport of #36727

`<TargetFrameworks />` -> `<TargetFramework />` (#36727)

  * `<TargetFrameworks />` -> `<TargetFramework />`
    - avoid useless transitions to inner builds
  * Remove most `$(BenchmarksTargetFramework)` use

Co-authored-by: Sébastien Ros <sebastienros@gmail.com>

- backport of #36718

Always use latest targeting packs (#36718)

  - also, only update latest `@(KnownFrameworkReference)` items
    - previously the updates applied e.g. to all Microsoft.NETCore.App items

  nit: expand `@(KnownFrameworkReference)` comments

[release/6.0] Update dependencies from dotnet/efcore

[release/6.0] Update dependencies from dotnet/efcore

- backport of #36449 and #36756

Dougbu/check.solution.filters (#36449)

  * Check solution filters
  - confirm all mentioned projects are in AspNetCore.sln
  - clean up CodeCheck.ps1
    - avoid aliases
    - rework long lines
    - avoid deprecated `dotnet run -p`
    - improve output a bit
    - correct whitespace
  - there can be only one
    - we have just one solution file
    - solution file should mention projects _once_

  * Add missing projects to AspNetCore.sln
  - Middleware.slnf contained projects that no longer exist eg. NodeServices
    - VS also sorted the file and VS 2019 added ARM64 configurations
  - a few other solution filters still referenced removed and moved projects
  - correct capitalization in some solution filters

  Note: Unable to load some WiX projects in VS 2019 or _any_ in VS 2022 (WiX extension unavailable for 2022)

  * Remove trailing comma in a solution filter

Put concatenated `string`s in parentheses (#36756)

  - follow-up to 779db7f3
  - errors occur but point to the `+` sign instead of displaying real problem

[release/6.0] Update dependencies from dotnet/efcore

[release/6.0] Update dependencies from dotnet/runtime

As part of https://github.com/dotnet/aspnetcore/pull/35017, I had consolidated the DefaultViewCompiler and DefaultViewCompilerProvider
types, largely as a clean up. The type DefaultViewCompilerProvider is looked up by the RuntimeCompilation package by name, and when making
this change, this code was also updated.

However, we've had two reports so far of users trying to use an 5.0 or earlier version of the runtime compilation package with a 6.0 app. In this case, the lookup
fails and the runtime compilation feature doesn't work as expected after this.

Fixes https://github.com/dotnet/aspnetcore/issues/35267

[release/6.0] Update dependencies from dotnet/runtime dotnet/efcore

* Fix nav item issues for org auth
* Fix razor web pages

Co-authored-by: Hao Kung <HaoK@users.noreply.github.com>

Co-authored-by: Aditya Mandaleeka <adityam@microsoft.com>

- dotnet/aspnetcore-internal#3918

* Fix uncompressed scenarios with DisableBuffering #36960
* Comments

* Support more nonbubbling media events

* Update .js files

Co-authored-by: Steve Sanderson <SteveSandersonMS@users.noreply.github.com>
Co-authored-by: Tanay Parikh <taparik@microsoft.com>

[release/6.0] Update dependencies from dotnet/runtime dotnet/efcore

- backport of #36424 to release/6.0
- make it a bit easier to test _everything_ in one go
- builds site extensions, publishes to BAR, and runs all aspnetcore-ci tests

Co-authored-by: Doug Bunting <6431421+dougbu@users.noreply.github.com>

Co-authored-by: Weihan Li <weihanli@outlook.com>

* Normalize the content root and improve errors
- When trying to compare content root paths, make sure the paths are normalized before doing so. Today we throw too aggresively when libraries try to set the content root, even if that would have resulted in a noop. This change normalizes the initial path and the attempted path before doing the comparison.
- We also improve the error message when the user tries to change the host settings, directing them to the correct API to use instead.

* PR feedbacj

* Make it static

* Resolve the full path to handle . and ..

* Linux paths

[release/6.0] Update dependencies from dotnet/runtime

[automated] Merge branch 'release/6.0-rc2' => 'release/6.0'

Co-authored-by: Stephen Halter <halter73@gmail.com>

* Fix alpine queue used for Helix

* Update Helix.Common.props

Co-authored-by: Will Godbe <wigodbe@microsoft.com>

* Update test to account for localized component names

* Support Titlecase/OtherLetter

* Update ComponentChildContentIntegrationTest.cs

* Add SupportLocalizedComponentNames Configurable Property

* PR Feedback

* Test supportLocalizedComponentNames configuration

* PR Feedback

* Update PublicAPI.Unshipped.txt

* RC2 Tooling Support for Support Localized Component Names (#36936)

[release/6.0] Update dependencies from dotnet/efcore

[release/6.0-rc2] Update dependencies from dotnet/arcade

[release/6.0] Update dependencies from dotnet/arcade

[release/6.0] Update dependencies from dotnet/efcore

* Update WiX to signed build (#36865)

- #12078

* Always download blazor-hotreload.js from app root (#36897)

The middleware that we inject always listens to the root of the app. While this might not play very nicely if the app
is running off a virtual path, listening to the root is what we do with the aspnet-browser-refresh.js script and we've had no issue
reports with it thus far.

Fixes https://github.com/dotnet/aspnetcore/issues/35555



* Improve Results.Problem and Results.ValidationProblem APIs (#36856)

* [release/6.0-rc2] Update sdk to 6.0.100-rc.2.21470.55 (#36783)

* Update sdk to 6.0.100-rc.2.21470.55

Co-authored-by: Will Godbe <wigodbe@microsoft.com>

Co-authored-by: Doug Bunting <6431421+dougbu@users.noreply.github.com>
Co-authored-by: Pranav K <prkrishn@hotmail.com>
Co-authored-by: Safia Abdalla <safia@microsoft.com>
Co-authored-by: Stephen Halter <halter73@gmail.com>
Co-authored-by: Will Godbe <wigodbe@microsoft.com>
Co-authored-by: Brennan <brecon@microsoft.com>

[release/6.0] Update dependencies from dotnet/efcore

* Update sdk to 6.0.100-rc.2.21470.55

* Add pragmas

* More pragmas

* One more

* Use preview features in tests

Co-authored-by: Will Godbe <wigodbe@microsoft.com>

Co-authored-by: Will Godbe <wigodbe@microsoft.com>

Bumps [src/submodules/spa-templates](https://github.com/dotnet/spa-templates) from `796e436` to `a64c11d`.
- [Release notes](https://github.com/dotnet/spa-templates/releases)
- [Commits](https://github.com/dotnet/spa-templates/compare/796e4363976fbd719468dc9466aa333ae82f7ae3...a64c11d4919e91f52ae042b58be2b2c346f27a39

)

---
updated-dependencies:
- dependency-name: src/submodules/spa-templates
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>

Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

The middleware that we inject always listens to the root of the app. While this might not play very nicely if the app
is running off a virtual path, listening to the root is what we do with the aspnet-browser-refresh.js script and we've had no issue
reports with it thus far.

Fixes https://github.com/dotnet/aspnetcore/issues/35555