Open lucky-skebe opened 5 years ago
Addition: Deleting the entire Intiface CLI folder and running the setup from the intifaceDesktop fixed the problem
Thanks for letting me know! It looks like the uninstaller may not be clearing everything out or something. There's most likely going to be a new version out today, hopefully that will fix this.
On Sun, Jun 30, 2019 at 10:45 AM lucky-skebe notifications@github.com wrote:
Addition: Deleting the entire Intiface CLI folder and running the setup from the intifaceDesktop fixed the problem
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/intiface/intiface-cli-csharp/issues/9?email_source=notifications&email_token=AAAIN2YKXJOHC3NB4MQSZSTP5DWLZA5CNFSM4H4NCIR2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODY4QRJY#issuecomment-507054247, or mute the thread https://github.com/notifications/unsubscribe-auth/AAAIN2352GH2R5PFNOGK3LLP5DWLZANCNFSM4H4NCIRQ .
Ok, looks like this is becoming a more common problem: https://metafetish.club/t/start-intiface-server-error/755
I still can't replicate locally, but I'll see about making some sort of validity check and recovery option in Intiface.
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 Abhngigkeit 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.