Creating extension does not create .vscode config

[apric0ts]

When creating extensions via extension manager, it creates a .vscode config file but this doesn't. So VSCode debugger does not work

[SchultzC]

Rather than using the extension manager, the recommended approach for creating a new extension is via ./repo.sh template new (Linux) or .\repo.bat template new (Windows)

The extension template most like the one from the extension manager is this one:

https://github.com/NVIDIA-Omniverse/kit-app-template/tree/main/templates/extensions/python_ui

Instructions exist there for generating the extension and adding to your application via the .kit file

[apric0ts]

Thanks for getting back to me so quick, apologies for not being clear. I used this template and the command you gave me to generate extensions. The extension generated from the kit-app-template's python_ui template does not build the .vscode folder with a launch.json file that I'd like to use, so I can debug my code with the VS Code Debugger Extension.

Creating extensions with the extension manager however does create this .vscode folder, which is why I brought that up.

[SchultzC]

I see. Thank you for clarifying. That file exists in kit-app-template/.vscode now. VS Code should be able to find it under the name "Python: Remote Attach"

After starting the debug session form VS Code it might be required to hit "refresh" on the VS Code Link extension to attach.