Changes

Chunks of code written by many contributors including Microsoft themselves that allow extra functionality to be loaded into VSC. The debugger itself is one such component, as is the Remote Access mechanism and an extension to work intelligently with Python code.

Chunks of code written by many contributors including Microsoft themselves that allow extra functionality to be loaded into VSC. The debugger itself is one such component, as is the Remote Access mechanism and an extension to work intelligently with Python code.

=====Remote Explorer=====

=====Remote Explorer=====

Access to the Remote Machine

Access to the Remote Machine. This an extension that needs to be installed to allow remote debugging.

=====Testing=====

=====Testing=====

====How do I set up VSC to use the debugger?====

====How do I set up VSC to use the debugger?====

The zynthian has specific setup elements that allow the system to run properly. These are outlined in a file called launch.json which VSC can generate if requested but can be manually created in a directory /zynthian/zynthian-ui/.vscode

The first requirement is the Remote Explorer mentioned above, use the extensions panel to search and install. Beyond this, the zynthian has specific setup elements that allow the system to run properly. These are outlined in a file called launch.json which VSC can generate if requested but can be manually created in a directory /zynthian/zynthian-ui/.vscode

Here is an example launc.json for debugging zynthian:

Here is an example launc.json for debugging zynthian:

==== How Do I access code on my zynthian from my host machine? ====

==== How Do I access code on my zynthian from my host machine? ====

We need to use  Visual Studio Code(VSC) Remote Explorer to allow us to add on to the zynthian and install enough of an environment to allow VSC to seamlessly pass code between the environment and the desktop machine.Frankly sometimes it feels like magic, and for anyone who has read my previous attempts to do this sort of thing you spent a lot of time making sure the shaky old connections required behaved as machines are restarted and stopped and broken and goodness knows what lse. VSC relly sorts this out nicely, and it's a blessing. Indeed it is so tenacious in how it manages connections that the following image is actual a bit of a manufactured effort, but worry no it does it all very well.  

We need to use  Visual Studio Code(VSC) Remote Explorer (remember to install the extension!) to allow us to add on to the zynthian and install enough of an environment to allow VSC to seamlessly pass code between the environment and the desktop machine. Frankly sometimes it feels like magic, and for anyone who has read my previous attempts to do this sort of thing you spent a lot of time making sure the shaky old connections required behaved as machines are restarted and stopped and broken and goodness knows what else. VSC really sorts this out nicely, and it's a blessing. Indeed it is so tenacious in how it manages connections that the following image is actual a bit of a manufactured effort, but worry no it does it all very well.