IDeviceDeploy

Remarks

The device manager knows what devices there are and this says what can be done to one. Building a player is a project, a target, a content build and a process — none of which belongs beside a list of machines, and all of which is why this assembly is constructible against a bare UiDocument.

⚠ Refusal is a sentence, not a boolean. Doc 20's first bar is that a verb which is not reachable right now is visibly not reachable — and "why not" is the half that stops somebody pressing a greyed button repeatedly. A console takes its build through the vendor's SDK; a phone needs a device provider that does not exist yet; each is a different sentence and none of them is "no".

Here rather than beside the implementation because both ends need to name it: the panel that offers the button and whatever in the editor can carry it out. Doc 36 § P3 — the two are in different assemblies now, and a contract owned by either would be a reference back to it.

Methods (2)

• string? Refuse(DeviceEntry device)

  Why this device cannot be deployed to, or if it can.

• void Deploy(DeviceEntry device)

  Builds a player and puts it on the device.

Used by (3)

• DiagnosticsModuleVixen.Editor.Diagnostics
• EditorApplicationVixen.Editor.App
• PlayerDeployVixen.Editor.App