Merge main into live

docs/core/compatibility/10.md

@@ -109,6 +109,7 @@ See [Breaking changes in EF Core 10](/ef/core/what-is-new/ef-core-10.0/breaking-
 | Title | Type of change    | Introduced version |
 |-------|-------------------|--------------------|
 | [More restricted annotations on InvokeMember/FindMembers/DeclaredMembers](reflection/10/ireflect-damt-annotations.md) | Behavioral/source incompatible | |
+| [Type.MakeGenericSignatureType argument validation](reflection/10/makegeneric-signaturetype-validation.md) | Behavioral change | |
 
 ## SDK and MSBuild
 
@@ -120,6 +121,7 @@ See [Breaking changes in EF Core 10](/ef/core/what-is-new/ef-core-10.0/breaking-
 | [Default workload configuration from 'loose manifests' to 'workload sets' mode](sdk/10.0/default-workload-config.md) | Behavioral change |
 | [Code coverage EnableDynamicNativeInstrumentation defaults to false](sdk/10.0/code-coverage-dynamic-native-instrumentation.md) | Behavioral change |
 | [dnx.ps1 file is no longer included in .NET SDK](sdk/10.0/dnx-ps1-removed.md) | Source incompatible |
+| [Double quotes in file-level directives are disallowed](sdk/10.0/file-level-directive-double-quotes.md) | Source incompatible |
 | [`dotnet new sln` defaults to SLNX file format](sdk/10.0/dotnet-new-sln-slnx-default.md) | Behavioral change |
 | [`dotnet package list` performs restore](sdk/10.0/dotnet-package-list-restore.md) | Behavioral change |
 | [`dotnet restore` audits transitive packages](sdk/10.0/nugetaudit-transitive-packages.md) | Behavioral change |

docs/core/extensions/dependency-injection/guidelines.md

@@ -22,7 +22,10 @@ If a class has many injected dependencies, it might be a sign that the class has
 
 ### Disposal of services
 
-The container is responsible for cleanup of types it creates, and calls <xref:System.IDisposable.Dispose%2A> on <xref:System.IDisposable> instances. Services resolved from the container should never be disposed by the developer. If a type or factory is registered as a singleton, the container disposes the singleton automatically.
+The container is responsible for cleanup of types it creates, and calls <xref:System.IDisposable.Dispose%2A> on <xref:System.IDisposable> instances. Services resolved from the container should never be disposed by the developer. The container disposes services automatically based on their lifetime:
+
+- **Transient** and **scoped** services are disposed at the end of the scope in which they were resolved. In apps that process requests, this is typically at the end of the request.
+- **Singleton** services are disposed when the service container is disposed, usually at application shutdown.
 
 In the following example, the services are created by the service container and disposed automatically:
 

docs/core/extensions/snippets/http/generated/Program.cs

@@ -10,7 +10,7 @@
 builder.Services.AddRefitClient<ITodoService>()
     .ConfigureHttpClient(client =>
     {
-        // Set the base address of the named client.
+        // Set the base address of the typed client.
         client.BaseAddress = new Uri("https://jsonplaceholder.typicode.com/");
 
         // Add a user-agent default request header.

docs/core/sdk/file-based-apps.md

@@ -363,6 +363,9 @@ Caching improves build performance but can cause confusion when:
 - Changes to implicit build files don't trigger rebuilds.
 - Moving files to different directories doesn't invalidate cache.
 
+> [!NOTE]
+> Concurrent invocations of a file-based app (for example, running more than one instance of the same file-based app in parallel) can cause errors due to contention over the build output files. To avoid this, first build the file-based app via `dotnet build file.cs` before starting the concurrent instances via `dotnet run file.cs --no-build`.
+
 ### Workarounds
 
 - Clear cache artifacts for file-based apps by using the following command: