Add missing connection string sections. (#1170)

* Add missing connection string sections. Fixes #1165

* Update docs/database/postgresql-entity-framework-component.md

docs/database/azure-cosmos-db-component.md

@@ -2,7 +2,7 @@
 title: .NET Aspire Azure Cosmos DB component
 description: This article describes the .NET Aspire Azure Cosmos DB component features and capabilities.
 ms.topic: how-to
-ms.date: 06/05/2024
+ms.date: 06/28/2024
 ---
 
 # .NET Aspire Azure Cosmos DB component
@@ -114,7 +114,7 @@ The recommended connection approach is to use an account endpoint, which works w
 ```json
 {
     "ConnectionStrings": {
-    "cosmosConnectionName": "https://{account_name}.documents.azure.com:443/"
+      "cosmosConnectionName": "https://{account_name}.documents.azure.com:443/"
     }
 }
 ```

docs/database/mysql-entity-framework-component.md

@@ -1,7 +1,7 @@
 ---
 title: MySQL Entity Framework Component
 description: MySQL Entity Framework Component
-ms.date: 06/05/2024
+ms.date: 06/28/2024
 ---
 
 # .NET Aspire Pomelo MySQL Entity Framework Component
@@ -94,7 +94,7 @@ And then the connection string will be retrieved from the `ConnectionStrings` co
 
 The `EnrichMySqlDbContext` won't make use of the `ConnectionStrings` configuration section since it expects a `DbContext` to be registered at the point it is called.
 
-See the [MySqlConnector documentation](https://mysqlconnector.net/connection-options/) for more information on how to format this connection string.
+For more information, see the [MySqlConnector documentation](https://mysqlconnector.net/connection-options/).
 
 ### Use configuration providers
 

docs/database/oracle-entity-framework-component.md

@@ -1,7 +1,7 @@
 ---
 title: Oracle Entity Framework Component
 description: Oracle Entity Framework Component
-ms.date: 06/03/2024
+ms.date: 06/28/2024
 ---
 
 # .NET Aspire Oracle Entity Framework Component
@@ -126,7 +126,7 @@ And then the connection string will be retrieved from the `ConnectionStrings` co
 
 The `EnrichOracleDatabaseDbContext` won't make use of the `ConnectionStrings` configuration section since it expects a `DbContext` to be registered at the point it is called.
 
-See the [ODP.NET documentation](https://www.oracle.com/database/technologies/appdev/dotnet/odp.html) for more information on how to format this connection string.
+For more information, see the [ODP.NET documentation](https://www.oracle.com/database/technologies/appdev/dotnet/odp.html).
 
 ### Use configuration providers
 

docs/database/postgresql-component.md

@@ -1,7 +1,7 @@
 ---
 title: .NET Aspire PostgreSQL component
 description: This article describes the .NET Aspire PostgreSQL component.
-ms.date: 06/05/2024
+ms.date: 06/28/2024
 ms.topic: how-to
 ---
 
@@ -86,6 +86,8 @@ And then the connection string will be retrieved from the `ConnectionStrings` co
 }
 ```
 
+For more information, see the [ConnectionString](https://www.npgsql.org/doc/connection-string-parameters.html).
+
 ### Use configuration providers
 
 The .NET Aspire PostgreSQL component supports <xref:Microsoft.Extensions.Configuration?displayProperty=fullName>. It loads the <xref:Aspire.Npgsql.NpgsqlSettings> from _:::no-loc text="appsettings.json":::_ or other configuration files by using the `Aspire:Npgsql` key. Example _:::no-loc text="appsettings.json":::_ that configures some of the options:

docs/database/postgresql-entity-framework-component.md

@@ -2,7 +2,7 @@
 title: .NET Aspire PostgreSQL Entity Framework Core component
 description: This article describes the .NET Aspire PostgreSQL Entity Framework Core component.
 ms.topic: how-to
-ms.date: 06/05/2024
+ms.date: 06/28/2024
 ---
 
 # .NET Aspire PostgreSQL Entity Framework Core component
@@ -82,6 +82,28 @@ var myService = builder.AddProject<Projects.MyService>()
 
 The .NET Aspire PostgreSQL Entity Framework Core component provides multiple configuration approaches and options to meet the requirements and conventions of your project.
 
+### Use a connection string
+
+When using a connection string from the `ConnectionStrings` configuration section, you provide the name of the connection string when calling `AddNpgsqlDbContext`:
+
+```csharp
+builder.AddNpgsqlDbContext<MyDbContext>("myConnection");
+```
+
+The connection string is retrieved from the `ConnectionStrings` configuration section:
+
+```json
+{
+  "ConnectionStrings": {
+    "myConnection": "Host=myserver;Database=test"
+  }
+}
+```
+
+The `EnrichNpgsqlDbContext` won't make use of the `ConnectionStrings` configuration section since it expects a `DbContext` to be registered at the point it is called.
+
+For more information, see the [ConnectionString](https://www.npgsql.org/doc/connection-string-parameters.html).
+
 ### Use configuration providers
 
 The .NET Aspire PostgreSQL Entity Framework Core component supports <xref:Microsoft.Extensions.Configuration?displayProperty=fullName>. It loads the <xref:Aspire.Npgsql.EntityFrameworkCore.PostgreSQL.NpgsqlEntityFrameworkCorePostgreSQLSettings> from configuration files such as _:::no-loc text="appsettings.json":::_ by using the `Aspire:Npgsql:EntityFrameworkCore:PostgreSQL` key. If you have set up your configurations in the `Aspire:Npgsql:EntityFrameworkCore:PostgreSQL` section you can just call the method without passing any parameter.
@@ -115,7 +137,7 @@ builder.AddNpgsqlDbContext<YourDbContext>(
     static settings => settings.ConnectionString = "YOUR_CONNECTIONSTRING");
 ```
 
-### Configure multiple DBContext classes
+### Configure multiple DbContext classes
 
 If you want to register more than one <xref:Microsoft.EntityFrameworkCore.DbContext> with different configuration, you can use `$"Aspire:Npgsql:EntityFrameworkCore:PostgreSQL:{typeof(TContext).Name}"` configuration section name. The json configuration would look like:
 

docs/database/sql-server-component.md

@@ -2,7 +2,7 @@
 title: .NET Aspire SQL Server component
 description: This article describes the .NET Aspire SQL Server component.
 ms.topic: how-to
-ms.date: 06/05/2024
+ms.date: 06/28/2024
 ---
 
 # .NET Aspire SQL Server component
@@ -91,6 +91,26 @@ For more information, see [External parameters](../fundamentals/external-paramet
 
 The .NET Aspire SQL Server component provides multiple configuration approaches and options to meet the requirements and conventions of your project.
 
+### Use a connection string
+
+When using a connection string from the `ConnectionStrings` configuration section, you provide the name of the connection string when calling `AddSqlServerClient`:
+
+```csharp
+builder.AddSqlServerClient("myConnection");
+```
+
+The connection string is retrieved from the `ConnectionStrings` configuration section:
+
+```json
+{
+  "ConnectionStrings": {
+    "myConnection": "Data Source=myserver;Initial Catalog=master"
+  }
+}
+```
+
+For more information, see the [ConnectionString](/dotnet/api/system.data.sqlclient.sqlconnection.connectionstring#remarks).
+
 ### Use configuration providers
 
 The .NET Aspire SQL Server supports <xref:Microsoft.Extensions.Configuration?displayProperty=fullName>. It loads the `MicrosoftDataSqlClientSettings` from configuration files such as _:::no-loc text="appsettings.json":::_ by using the `Aspire:SqlServer:SqlClient` key. If you have set up your configurations in the `Aspire:SqlServer:SqlClient` section, you can just call the method without passing any parameter.
@@ -116,7 +136,7 @@ The following example shows an _:::no-loc text="appsettings.json":::_ file that
 You can also pass the `Action<MicrosoftDataSqlClientSettings>` delegate to set up some or all the options inline, for example to turn off the `DisableMetrics`:
 
 ```csharp
-builder.AddSqlServerSqlClientConfig(
+builder.AddSqlServerClient(
     static settings => settings.DisableMetrics = true);
 ```
 
@@ -139,10 +159,10 @@ If you want to add more than one `SqlConnection` you could use named instances.
 }
 ```
 
-To load the named configuration section from the json config call the `AddSqlServerSqlClientConfig` method by passing the `INSTANCE_NAME`.
+To load the named configuration section from the json config call the `AddSqlServerClient` method by passing the `INSTANCE_NAME`.
 
 ```csharp
-builder.AddSqlServerSqlClientConfig("INSTANCE_NAME");
+builder.AddSqlServerClient("INSTANCE_NAME");
 ```
 
 ### Configuration options

docs/database/sql-server-entity-framework-component.md

@@ -2,7 +2,7 @@
 title: .NET Aspire SqlServer Entity Framework Core component
 description: This article describes the .NET Aspire SQL Server Entity Framework Core component.
 ms.topic: how-to
-ms.date: 06/05/2024
+ms.date: 06/28/2024
 ---
 
 # .NET Aspire SqlServer Entity Framework Core component
@@ -74,6 +74,28 @@ var myService = builder.AddProject<Projects.MyService>()
 
 The .NET Aspire SQL Server Entity Framework Core component provides multiple configuration approaches and options to meet the requirements and conventions of your project.
 
+### Use connection string
+
+When using a connection string from the `ConnectionStrings` configuration section, you provide the name of the connection string when calling `builder.AddSqlServerDbContext<TContext>()`:
+
+```csharp
+builder.AddSqlServerDbContext<MyDbContext>("myConnection");
+```
+
+The connection string is retrieved from the `ConnectionStrings` configuration section:
+
+```json
+{
+  "ConnectionStrings": {
+    "myConnection": "Data Source=myserver;Initial Catalog=master"
+  }
+}
+```
+
+The `EnrichSqlServerDbContext` won't make use of the `ConnectionStrings` configuration section since it expects a `DbContext` to be registered at the point it's called.
+
+For more information, see the [ConnectionString](/dotnet/api/system.data.sqlclient.sqlconnection.connectionstring#remarks).
+
 ### Use configuration providers
 
 The .NET Aspire SQL Server Entity Framework Core component supports <xref:Microsoft.Extensions.Configuration?displayProperty=fullName>. It loads the <xref:Aspire.Microsoft.EntityFrameworkCore.SqlServer.MicrosoftEntityFrameworkCoreSqlServerSettings> from configuration files such as _:::no-loc text="appsettings.json":::_ by using the `Aspire:Microsoft:EntityFrameworkCore:SqlServer` key. If you have set up your configurations in the `Aspire:Microsoft:EntityFrameworkCore:SqlServer` section you can just call the method without passing any parameter.