|4.0.0-devel-202006 Monthly Release|
| TIE-76||Fixed||Visual Studio Code for Linux fails attempting to add a device via serial||All supported modules||Moses (IDE Backend)||Low||No|
Description: Customer in referenced community post has an issue in the VScode extension where attempting to add a device via serial seems to fail.
| TIE-94||Fixed||Command to create ASP.NET application fails if the extension is not loaded||Visual Studio Code Extension||Low||No|
Description: Visual studio code activates the extensions on different event. Torizon extension is activated and loaded when an existing project is opened, when a new python or .NET application is create or when the Torizon bar is used.
ASP.NET app creation command was not considered an activation event and so it fails if you try to execute it when the extension is not already loaded.
Workaround: Open the torizon bar by clicking on the Torizon logo in the Visual Studio code Activity Bar on the left side of VS Code main window, this will activate the extension and allow you to run the ASP.NET application create command.
| TIE-6||New Feature||ASP.NET templates for Visual Studio Code Extensions||Visual Studio Code Extension||Low||No|
Description: ASP.NET provides multiple application types. Current template uses basic MVC, but this may not fit customer’s requirement.
New templates has been added for most of the ASP.NET application types supported by the “dotnet new” command.
A more flexible template definition (via YAML file) has been added and may allow definition of more templates also for other languages.
| TIE-65||Fixed||Error adding device: this.refresh is not a function in VS Code Extension||Visual Studio Code Extension||Low||No|
Description: Error in Visual Studio Code extension when adding device from network
|4.0.0-devel-202005 Monthly Release|
| TIE-74||Fixed||SSH error on Windows when debugging a .NET application from a folder that is not under user's home||Visual Studio Code Extension||Low||No|
Description: When developing a .NET application that is stored in a folder that is not under the user home or is accessible to all users, you get an error when trying to start debugger.
On the debug console you can see an error message from SSH complaining about the fact that the permissions for the key file are too open.
Workaround: Move your project under your home folder or change it's access rights to make it accessible only from your user.
| TIE-71||Fixed||Weird behavior in the appconfig_0 folder||Visual Studio Code Extension||Low||No|
Description: An error was causing a weird behavior in the appconfig_0 folder of the VSCode plugin.
| TIE-64||Fixed||Visual Studio error: Object reference not set to an instance of an object||Moses (IDE Backend), Visual Studio Extension||Low||No|
Description: On one of the PCs where the extension has been tested, when executing "Deploy and Debug Torizon Application", a dialog pops-up with the error "Object reference not set to an instance of an object".
From this point onwards, it is impossible to deploy and debug Torizon applications, even if a new project is created or Visual Studio is restarted.
There are issues also accessing the debugging options of the project and of any project created using the Visual Studio for Linux extension.
Workaround: Uninstall and Reinstall Visual Studio.
|4.0.0-devel-202004 Monthly Release|
| TIE-108||Fixed||Error on 64-bit .NET Core containers||Visual Studio Code Extension||Low||No|
Description: 64-bit .NET Core container does not work
|Issues in this section are not scheduled yet. Please get in touch with our support if you need to have any of these issues scheduled.
| TIE-77||Known Issue||extraparms setting not available in Visual Studio 2019 Application Properties dialog||Visual Studio Extension||No|
Description: This setting can be used to configure additional settings related to container execution.
It's available in Visual Studio Code UI, but not in Visual Studio 2019.
| TIE-98||Known Issue||VS Extension: Adding outside files/folder to the project causes compilation to fail||All supported modules||Moses (IDE Backend)||Low||No|
Description: When trying to add files/folder that are located outside of the the main VS project folder the project folder structure then gets altered. This alteration of the folder structure then causes things like compilation and debugging to fail.
| TIE-14||Known Issue||Apply environment settings to Dockerfile and ssh connection in debug builds||Visual Studio Code Extension||Low||No|
Description: Currently settings added via the "env" property are applied only when the application runs in the release container.
Debugger connects over SSH and those variables are not defined when the application runs.
| TIE-62||Known Issue||VS Code Extension - Error Deploying to Device using WSL 2: can't find a valid IP for apalis-imx8||Visual Studio Code Extension||Low||No|
Description: On Windows 10 Home and WSL 2, when deploying to a device, the following error occurs several times: "Error (545) - Can't find a valid IP for board name". NOTE: Windows 10 Home and WSL 2 are not supported at the moment.
Workaround: Retry to deploy (press F5 for instance) until it works. It may work on 1 out of 10 tries.
| TIE-1||Feature Request||Support C/C++ development in VS Code providing cross-compiling and remote debugging||Visual Studio Code Extension||Low||No|
Description: Developing applications in C/C++ will be supported by the Visual Studio Code extension for Torizon. Cross-compilation and remote debugging will be supported.
| TIE-12||Known Issue||Sometimes Visual Studio displays the message "Visual Studio stopped responding for X seconds"||Visual Studio Extension||Low||No|
Description: Sometimes Visual Studio displays the message "Visual Studio stopped responding for X seconds. Disabling the extension Torizon Visual Studio Development Tools might help". It may be possible to optimize the plugin to avoid it from happening. Despite the latency caused by Visual Studio becoming non-responsive, there are no side-effects reported.
Workaround: Just click "Don't report this extension again".
|Issues in this section are not planned to be addressed. Please get in touch with our support if you need to have any of these issues addressed.
| TIE-17||Feature Request||Provide LICENSE file for VS Code extension||Visual Studio Code Extension||Low||No|
Description: The Visual Studio marketplace allows providing license information for extensions. Visual Studio Code extension for Torizon has an empty license at the moment.
| TIE-56||Known Issue||VS Code Extension and Python: Debug instance does not start||Visual Studio Code Extension||Low||No|
Description: If a debug instance is started (press F5), stopped (press Shift + F5) and re-started (press F5) in a short time window (less than 5 seconds), the debug instance may simply not start on the second time.
Workaround: Wait a few seconds and re-start the deploy and debug (press F5).
| TIE-82||Known Issue||Error (500) When Try to Debug .NET App||Visual Studio Code Extension||Low||No|
Description: Launching debugger for a .NET app in Visual Studio code a popup reporting error 500 appears.