Intiface Desktop shows an error message when trying to start a server using secure websockets:

Command failed: C:\Program Files (x86)\IntifaceCLI\IntifaceCLI.exe --frontendpipe --stayopen --wssecureport 12346 --wscertfile C:\Users\...\AppData\Local\Intiface\cert.pem --wsprivfile C:\Users\...\AppData\Local\Intiface\privkey.pem --log Info

AggregateException was unhandled. One or more errors occurred.
---> System.Exception: Pem certificate C:\Users\...\AppData\Local\Intiface\cert.pem could not be loaded
---> System.Exception: The Method "ReadPemCertificateWithPrivateKey" has failed.
---> System.IO.FileLoadException: Could not load file or assembly "BouncyCastle.Crypto, Version=1.8.4.0, Culture=neutral, PublicKeyToken=0e99375e54769942" or one of its dependencies. The specified module could not be found.
[...]

It looks like the Windows release of Intiface CLI v0.4.5 comes bundled with version 1.8.5 of the BouncyCastle.Crypto.dll assembly.
However, the Buttplug.Server.Connectors.WebsocketServer.dll library requires version 1.8.4 of that assembly.

As a workaround, users can get version 1.8.4 of BouncyCastle.Crypto.dll from bouncycastle.org and replace the file in the installation directory (C:\Program Files (x86)\IntifaceCLI).

Affected versions:

• Intiface Desktop version: 14.0.0
• Intiface Engine version: 0.4.5
• OS: Windows 10

They're all using the same factory, so we can just bounce connections as needed once one is live.

So that we can actually load user settings into the CLI.

Right now they're just "insecureport" and "secureport" which is going to be a problem if we add TCP transports at some point.

For preserving device managers between connections.

Instead of just specifying a server and 2 ports, just specify the ports and run the server if either/both port options exists.

Right now it just prints "1".

After an Update via Intiface Desktop I got a Massage like this when trying to start the server:

{ "reason": "Command failed: E:\Program Files (x86)\IntifaceCLI\IntifaceCLI.exe --frontendpipe --stayopen --wsinsecureport 12345 --log Info\n\nUnbehandelte Ausnahme: System.IO.FileLoadException: Die Datei oder Assembly "CommandLine, Version=2.4.3.0, Culture=neutral, PublicKeyToken=de6f01bd326f8c32" oder eine Abh�ngigkeit davon wurde nicht gefunden. Die gefundene Manifestdefinition der Assembly stimmt nicht mit dem Assemblyverweis �berein. (Ausnahme von HRESULT: 0x80131040)\r\n bei IntifaceCLI.Program.Main(String[] args)\n" }

(Sorry for the german Error message)

I tried manually replacing the CommandLine.dll with the 2.4.3 version and suddenly I got a different message (wrong version for yamldotnet I believe). So I'm pretty sure the programm still requires the old versions but the dlls got updated.

We should be able to persist device ids outside of sessions, so we can cycle sessions instead of having to keep device managers alive in-process.