vscode-as3mxml: Unable to Build

I have set everything up as your instructions state to. However when I attempt to build I am getting the following error:

The terminal process terminated with exit code: 2

Terminal will be reused by tasks, press any key to close it.

Under the Problems tab I see this

A fatal error occurred. Error checking has been disabled, except for simple syntax problems.

asconfig.json

{
	"config": "flex",
	"compilerOptions": {
		"output": "bin/manufacturer.swf"
	},
	"files":
	[
		"./manufacturer.mxml"
	]
}

settings

"nextgenas.java": "/usr/local/bin/java",
"nextgenas.sdk.framework": "/Applications/Adobe Flash Builder 4.7/sdks/3.6.0"

Any assistance would be appreciated as I cannot seem to get Flash Builder to run without locking up on my system so it is completely unusable. I would love for the ability to build using vs-code

Building the project works fine in Flash Builder, however editing files in Flash Builder leads to the application hanging so currently I am editing in VSCode and building in Flash Builder, would be nice to get this to work in VSCode so I could just blow away Flash Builder.

About this issue

  • Original URL
  • State: closed
  • Created 6 years ago
  • Comments: 22 (10 by maintainers)

Most upvoted comments

Yeah, it’s probably a change in Insider’s. It sounds like they’re going to let me define an identifier in the extension that you can reference in launch.json without also adding it to tasks.json manually. That should be a good improvement!

See the Build automatically before debugging section in Debug a SWF embedded in HTML with Visual Studio Code. It’s kind of the opposite idea. You ask VSCode to debug (which will launch the HTML file in the browser), but preLaunchTask makes it build your SWF first.

If you ever want to see exactly which compiler options Flash Builder is using, you can add the dump-config compiler option. It will create a config file that can even be passed to the command line compiler with load-config.

-dump-config=my-dumped-config.xml