You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: Documentation/docs/how-to/client-certificates.md
+8Lines changed: 8 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -191,3 +191,11 @@ A couple tips on the above example:
191
191
192
192
TLS negotiation with client certificates is based on the `X509Certificate2` class. See the [official
193
193
.NET documentation](https://learn.microsoft.com/en-us/dotnet/api/system.security.cryptography.x509certificates.x509certificate2?view=net-8.0) for more options and information.
Copy file name to clipboardExpand all lines: Documentation/docs/how-to/configure-logging.md
+5-1Lines changed: 5 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,4 +1,4 @@
1
-
# Configure HiveMQtt Logging
1
+
# Configure Logging
2
2
3
3
The HiveMQtt package uses [NLog](https://github.com/NLog/NLog) and can be configured with a configuration file (`NLog.config`). Having this file in the same directory of your executable will configure the HiveMQtt logger to output as configured:
4
4
@@ -32,3 +32,7 @@ Setting `minlevel` to `Trace` will output all activity in the HiveMQtt package d
*[Authentication with Username and Password - MQTT Security Fundamentals](https://www.hivemq.com/blog/mqtt-security-fundamentals-authentication-username-password/)
Copy file name to clipboardExpand all lines: Documentation/docs/how-to/set-lwt.md
+15-12Lines changed: 15 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,8 +4,7 @@ The Last Will and Testament support of MQTT can be used to notify subscribers th
4
4
5
5
For a more in-depth explanation, see [What is MQTT Last Will and Testament (LWT)? – MQTT Essentials: Part 9](https://www.hivemq.com/blog/mqtt-essentials-part-9-last-will-and-testament/).
6
6
7
-
8
-
# LastWillAndTestament
7
+
## Using LastWillAndTestament
9
8
10
9
This example instantiates the `LastWillAndTestament` in the `HiveMQClientOption` class. This is then sent to the broker in the `connect` operation.
11
10
@@ -37,12 +36,11 @@ var disconnectResult = await client.DisconnectAsync(disconnectOptions).Configure
37
36
38
37
Because the client above disconnected with `DisconnectReasonCode.DisconnectWithWillMessage`, subscribers to the `last/will` topic will receive the Last Will and Testament message as specified above.
39
38
40
-
# LastWillAndTestament Builder Class
39
+
## The LastWillAndTestament Builder Class
41
40
42
-
As an ease-of-use alternative, the HiveMQtt client offers a `LastWillAndTestamentBuilder` class to more easily define a last will and testament class.
41
+
As an ease-of-use alternative, the HiveMQtt client offers a `LastWillAndTestamentBuilder` class to more easily instantiate a `LastWillAndTestament` class.
43
42
44
43
```csharp
45
-
46
44
varlwt=newLastWillAndTestamentBuilder()
47
45
.WithTopic("last/will")
48
46
.WithPayload("last will message")
@@ -56,13 +54,18 @@ var lwt = new LastWillAndTestamentBuilder()
*[TaskCompletionSource<TResult> Class (System.Threading.Tasks)](https://learn.microsoft.com/en-us/dotnet/api/system.threading.tasks.taskcompletionsource-1?view=net-8.0)
0 commit comments