Start my deployed iot app on RPI via PowerShell

[Gruber]

Hi,

I have tested the IOT sample for I2C communication with RPI and all is working well when I run this from Visual Studio.
Now I would like to start executing my deployed app via PowerShell or other terminal without VS.

I have added my app to startup and this works but I would like to start at my own discretion so to speak. How do I do this?

Thanks in advance//G

[SebastianM]

Hi,

good question.
But I don't think it is possible right now.....
http://ms-iot.github.io/content/win10/t ... eUtils.htm
(only see Options to set the Startup app)

Maybe we have to think about it as "one app device".


Sebastian

[Gruber]

Thanks for the quick reply,

Yup, one app device it is, at the moment.
The startup process is executing the app without VS debugging it so why can't we do it??
Maybe it is possible to start process from another app. Have to do some more digging here.

//G

[SebastianM]

Hi again,

as far as i understood the Debugger should Launch at Startup (I assume: also if you defined your own app as Startup app):
http://ms-iot.github.io/content/win10/SetupRPI.htm
(last line)

Also please take a look at this:

•To be able to deploy applications from Visual Studio 2015, you will need to make sure the Visual Studio Remote Debugger is running on your Windows IoT Core device. The remote debugger should launch automatically at machine boot time. To double check, use the tlist command to list all the running processes from powershell. There should be two instances of msvsmon.exe running on the device.

• It is possible for the Visual Studio Remote Debugger to time out after long periods of inactivity. If Visual Studio cannot connect to your Windows IoT Core device, try rebooting the device.

(source: http://ms-iot.github.io/content/win10/s ... rShell.htm at the bottom)

Did you check for the two msvsmon.exe instances?

Good luck

Sebastian

[Gruber]

hello,

Deployment is working and the debug server is running even after I have added my app to startup, so no problem there.
There seem to be another problem with startup apps though.
When your deployed app is placed as startup app it is impossible kill the process it keeps popping up with a new processID again. There seem to be a process in the background that keep it running no matter what.
Is this normal behaviour?

//G

[jtanner_msft]

If you just want to deploy and run a Universal App (.Appx) that you’ve built to another system you can do that using the WebB interface.

Open a web browser and enter: http://<ip address> where the IP is your Rpi2 device.

Click on the ‘App’ tab, and you will see the option to install an AppX onto the device. Once it’s been installed you can then select it and set it to be the running app.

This way you can avoid using VS for the deployment if you wish.

I hope that helps.