-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Command run with MS app return an error #9
Comments
also I did add its path to my environmental variables the error message went away.. but still didn't run app in desktop 1 |
Probably has something to do with this Process.Start from System.Diagnostics, relating doc is here. Maybe this or that migh help. So you could try: Maybe also have something to do with UseShellExecute : Just ideas. |
After some testing it aper that the app is to slow to start and when vdesk try to move the window in the correct desktop, the window does't exit. |
going to assume -w switch will work on next revision.. as current vdesk doesn't recognize the switch. |
@cruzer619 Yeah, wait for next release. |
@LittleVaaty just installed latest release.. and no-switch is not working. ran on desktop 3 and outlook runs on desktop 3 instead of desktop 1. Removing the no-switch does run on desktop 1. vdesk run --on 1 --no-switch -w 1000 "C:\Program Files\Microsoft Office\root\Office16\OUTLOOK.EXE" Also making wait time longer then 1000 gets this error: <3>VDesk.Commands.RunCommand[0] Element not found. (0x8002802B (TYPE_E_ELEMENTNOTFOUND)) |
Trying to run this command. Outlook opens but on the same desktop as I'm running the command on, Desktop 3.
C:\temp\Downloads>VDesk run --no-switch --on 1 "C:\Program Files\Microsoft Office\root\Office16\OUTLOOK.EXE"
<3>VDesk.Commands.RunCommand[0] Element not found. (0x8002802B (TYPE_E_ELEMENTNOTFOUND))
Windows version: 10.0.22621.3447
The text was updated successfully, but these errors were encountered: