Ticket Created
over 3 years ago

WERETECH-12396

vscode v1.0.2 debug launcher is broken

In the last vscode extension when you launch "execute and debug", the application is not compiled any more... then not found and not launched

If you have an old build, it launches it.... and you can loose 1 hour to understand why you don't see your changes...

If you delete the launch.json conf file. if will build again, but the name of the build is not the right one, so it won't launch.

To summarize, it's buggy, not tested.

SDK 4.1.1 is also full of bugs.

I'm bored to raise bugs...

_>exit

bobino75
  • over 3 years ago in reply to Brandon.ConnectIQ

    I just ran into this issue also. 8 days is a long time to let something like this go, . Perhaps there could be pinned forum post with "known issues" that we can check first, rather than having to crawl through the bug list to see if something has been reported? If the OP wasted an hour and I wasted about the same, that's likely a lot of hours lost across the developer community. Cry

    For those running into this issue, if your project name/folder has special characters (my issue was with dashes), then those will be removed and so while your project name might be something like "Awesome-APP-by-Douglas" (which is assigned to the launch.conf variable of ${workspaceFolderBasename}, the resulting PRG file will actually end up being "AwesomeAPPbyDouglas.PRG". So the solution is to modify your launch.conf file and change instances of the ${workspaceFolderBasename} with the filename that is actually generated.

  • over 3 years ago

    We believe we already have a fix for this issue, and will make it available in an upcoming VS Code Extension release. This can happen with extension v1.0.2 if you use something other than letters, numbers, and underscores in the project's directory name. Apologies for the inconvenience!