No Build tasks in VSCode

[Ron5s]

Last night I was able to see all the available build tasks in VSCode, but today they are gone and when I initialize a new project (F1) pressing f5 does not run the debugger, it looks like the .vscode file is not created. Not sure if this is an extension issue or VSCode issue or both. I am a little perplexed by this considering I did nothing to the computer overnight.

Thanks for the help,
Ron

[RobDangerous]

Happens to me as well, looks like vscode doesn't even activate the Kha extension anymore.

[Ron5s]

I see. Thank you for letting me know. Hopefully this will get fixed soon.

[juakob]

Same here, on Wednesday we did 10 installation and all work fine. Today it stop working on my machine too. Same here F1 kha init looks like the only working command. Did a clean install, but nothing seems to work. Can't build old projects ether now.

[Ron5s]

I'm glad I'm not the only one. Thanks for replying.

[RobDangerous]

Fixed in Kode/vscode-kha@5c8743ad, update already published. Yesterday's vshaxe update destroyed an old hack of mine. Serves me well is what @Gama11 secretly thinks for sure.

[Ron5s]

That works. Thank you for the quick turn around. Although it seems that projects generated prior to this update a have issues. But it might be as simple as generating a new project and coping over the source code. Ill have to see.

[Gama11]

Huh, interesting... I actually insisted on measures to avoid abuse like that for the newly introduced haxelibExecutable API, but I thought the old haxeExectuable API would continue to work as-is.

But yes, I have to admit - while this wasn't intentional (I would have given you forewarning), I'm definitely happy that the Kha extension now uses the proper API for this, which should work much better for several reasons. ;)

[RobDangerous]

Please delete the .vscode folder in the project and see if that helps.

[Ron5s]

Unfortunately that does not help. :(

[RobDangerous]

Interesting. Are you sure that's related to today's changes? There also was a rework in how electron debugging works two weeks ago. And could you maybe send me a project folder that behaves like that?

PS: Getting some sleep now so the next answers have to wait a little.

[Ron5s]

No worries, sleep well. Ill put up a small base project that exhibits the problem. Everything worked fine before the issues I had today. Thank you for the help.

Ron

[Ron5s]

Here is an old base project that exhibits the problem I described. Thank you.

Base Project.zip

[RobDangerous]

Works for me... but that gave me an idea: Update Kha, the changes from two weeks ago required a change to Kha.

[Ron5s]

So I updated Kha, but it had no effect. I also uninstalled everything including the extensions, I then created a new project and copied over the sources folder from the project I ziped and attached to this thread. That did not work. The problem is the build path was not set, it was empty. I typed build and now it all works fine. Not sure why that was not filled in though. Thanks for all of your help.

Ron

[RobDangerous]

Build path was not set - how and where? And typing build, what does that mean?

[Ron5s]

Im not sure how it was not set, but it was not set. But I added "build" as the relative path here:

[RobDangerous]

Ah, guess you accidentally changed it then when you tried to clean things up.

[Ron5s]

Yea that would probably be the case. Thanks for the help.