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
/// Message sent by the IDE to indicate that a target application has just been launched.
6
-
/// The dev-server will correlate this registration with a later runtime connection (AppIdentityMessage) using the MVID.
6
+
/// The dev-server will correlate this registration with a later runtime connection (`AppLaunchMessage` with `Step = Connected`) using the MVID, Platform and IsDebug.
7
7
/// </summary>
8
8
/// <param name="Mvid">The MVID (Module Version ID) of the head application assembly.</param>
9
9
/// <param name="Platform">The target platform (case-sensitive, e.g. "Wasm", "Android").</param>
Copy file name to clipboardExpand all lines: src/Uno.UI.RemoteControl.Server/AppLaunch/ApplicationLaunchMonitor.md
+11-6Lines changed: 11 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@
5
5
- You tell it that an app was launched, then you report when a matching app connects. It matches them 1:1 in launch order and handles timeouts.
6
6
- When a launched application fails to connect, it is reported as a timeout thru the OnTimeout callback.
7
7
- It is thread-safe / Disposable.
8
-
- It used the MVID as the key. This is the _Module Version ID_ of the app (head) assembly, which is unique per build. More info: https://learn.microsoft.com/en-us/dotnet/api/system.reflection.module.moduleversionid
8
+
- It uses a composite key: MVID + Platform + IsDebug. The MVID is the _Module Version ID_ of the app (head) assembly, which is unique per build. More info: https://learn.microsoft.com/en-us/dotnet/api/system.reflection.module.moduleversionid
9
9
10
10
## How to use
11
11
### 1) Create the monitor (optionally with callbacks and a custom timeout):
@@ -54,13 +54,18 @@ When integrated in the dev-server, the monitor emits telemetry events (prefix `u
54
54
55
55
`latencyMs` is the elapsed time between registration and connection, measured internally. `timeoutSeconds` equals the configured timeout.
56
56
57
-
## IDE / Runtime Messages
58
-
To enable correlation end-to-end, two messages flow through the system:
57
+
## Integration points (IDE, WebSocket, HTTP)
58
+
The dev-server can receive registration and connection events through multiple channels:
0 commit comments