Skip to content

Commit f31abd6

Browse files
committed
Formatting edits to C# section
1 parent 8b01c74 commit f31abd6

File tree

1 file changed

+0
-4
lines changed

1 file changed

+0
-4
lines changed

includes/iot-hub-howto-cloud-to-device-messaging-dotnet.md

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -41,8 +41,6 @@ A device app can authenticate with IoT Hub using the following methods:
4141

4242
The [DeviceClient](/dotnet/api/microsoft.azure.devices.client.deviceclient) class exposes all the methods required to receive messages on the device.
4343

44-
### Supply the connection parameters
45-
4644
Supply the IoT Hub primary connection string and Device ID to `DeviceClient` using the [CreateFromConnectionString](/dotnet/api/microsoft.azure.devices.client.deviceclient.createfromconnectionstring) method. In addition to the required IoT Hub primary connection string, the `CreateFromConnectionString` method can be overloaded to include these *optional* parameters:
4745

4846
* `transportType` - The transport protocol: variations of HTTP version 1, AMQP, or MQTT. `AMQP` is the default. To see all available values, see [TransportType Enum](/dotnet/api/microsoft.azure.devices.client.transporttype).
@@ -184,8 +182,6 @@ You can connect a backend service to IoT Hub using the following methods:
184182

185183
#### Connect using a shared access policy
186184

187-
##### Supply the connection string
188-
189185
Connect a backend application to a device using [CreateFromConnectionString](/dotnet/api/microsoft.azure.devices.serviceclient.createfromconnectionstring). In addition to the required IoT Hub primary connection string, the `CreateFromConnectionString` method can be overloaded to include these *optional* parameters:
190186

191187
* `transportType` - `Amqp` or `Amqp_WebSocket_Only`.

0 commit comments

Comments
 (0)