Etienne wrote: ↑06 Jun 2020, 05:00
lerou, thanks for your time with this question.
yeah, I just realised, I didn't anwer your question at all. Sorry for that.
Etienne wrote: ↑06 Jun 2020, 05:00
Your answer goes against what Karol replied. He says you
can use the VPR's
full path and it does not need to be in the Ventuz Project so I should not need to deal with VMSClient.Proj. That being said, in my experience, that is not possible. It's the first approach I tried. Also, I already have code that reads the Projects and looks for the VPR in there, then launches it by ID. This doesn't work when you copy a new VPR to a system and VMS hasn't scanned its Projects folders.
I just tried it in my remoting tool and I can confirm that using VMSClient.Start with an absolute path outside the VMS search dirs doesn't work.
I also tried manipulating the VMS Configuration, but as you already pointed out, the required methods (SetCFG, SetCFGAsync) have not been implemented.
So there seems to be no straight forward way to deal with this. A possible hack would be to change the VMS config file which includes the VMS search paths. It's located in the public documents near the default location for Ventuz projects:
C:\Users\Public\Documents\Ventuz6\Configuration\VMS
It's a simple XML file that you could read, alter and then use the VMS to look for projects and start them. I'm not sure if this is any better then to copy the VPRs to the public directoy to begin with.