How do you change remote system on VS extension

I tried to connect a 2nd target to the “getting started” Hello World project to see if I can get that going. The extension in Torizon Devices has detected and seemed to connect to the new device but when I go to do a debug and deploy it keeps going to the old system. I deleted the old system from Torizon Devices. I went into the HelloWorld property pages and changed the IP address to the correct on for the 2nd target. I can connect with SSH from the Torizon Devices pane. When I do the Deploy and Debug Torizon Application it says :

Severity	Code	Description	Project	File	Line	Suppression State
Error		Could not connect to the remote system. Please verify your connection settings, and that your machine is on the network and reachable.	HelloWorld	C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Microsoft\VC\v160\Application Type\Linux\1.0\Linux.targets	441	

Where else might there still be pointers to the old target? How do I change the target? Or have two targets and switch between the two during debug? Thanks.

Regards,
Chip

Project Properties->Configuration Properties->General->Remote Build Machine it has the old IP address:

192.168.1.137 (username=torizon, port=22, authentication=Password)

It insists on that. If you try to change that and hit apply or OK it changes it back. I have no idea where it’s hiding the original IP address to get it back.

Under Project Properties->Configuration Properties-> Debugging->Remote Debug Machine it would prefer the old IP address. It let me put in the new IP address but has it highlighted because it is not happy with it.

What I would expect would be something like right click on the target in Torizon Devices and say “select” or “connect” but somehow things are never that simple.

How do I change the target?

Regards,
Chip

I believe the “Remote Build Machine” option doesn’t mean the device/module. Technically the remote build machine is where the application gets compiled/built. For Torizon applications this means your development machine itself so this IP address should be localhost or such.

As for selecting your target device, when the application gets built and then ready to be deployed a dialog should come up that let’s you select which Torizon device to deploy it to as shown here: https://developer.toradex.com/getting-started/module-2-first-steps-with-torizon/build-and-run-your-first-c-application-arm64?som=apalis-imx8&board=ixora-carrier-board&os=torizon&desktop=windows#step-16

Do you not see this dialog pop up?

Hi Jeremias,

Unfortunately we don’t get that far. I don’t want to recreate an application from scratch. I have the application that I was trying on the first Apalis module I had and I just wanted to see that it would do the same thing on the 2nd module. I expect it to likewise fail the build if it gets to that point but it errors out with not being able to connect before it gets to that point. My first module IP address was 192.168.1.137. DHCP put this 2nd module at 192.168.1.138. All the references in the project are still 192.168.1.137 although I deleted the first module from the Toradex Devices list. If I manually edit the fields to 192.168.1.138 they revert back to 192.168.1.137. There’s obviously a setting somewhere that’s holding the old value that is controlling things.

Regards,
Chip

link text

Hi Jeremias,

Install of the early access VS extension failed. I’ve attached the log file for the installation. Some component seems to be missing. My VS is 16.7.2

Regards,
Chip

Hi Jeremias,

I got a paid license, installed 16.7.0. I now have 4 VS installs on my machine. Went through the whole getting-started setup from scratch. Found and connected to the (2nd) target at 192.168.1.138 in Torizon Devices. Created a whole new project. Went to build and it still went back and tried to access the first module I ever did at 192.168.1.137. Where has it put that address that it can be found by a new VS install, new Toradex extension install, new Torizon Device and new project? Y’all didn’t put something in the registry did you?

Regards,
Chip

So I just learned that our extension creates a folder under your Windows home folder, under whichever user by the name .moses. In this folder is where device connection information gets stored. This folder doesn’t get wiped or cleared on uninstalls which is why you’re seeing it persist throughout all this.