How to force ANEs unpackaging for release build?

[Adolio]

Hello,

I'm trying to enforce the unpackaging of ANEs in release builds (for ADL testing).

I found this option:

vscode-as3mxml/asconfigc/src/main/java/com/as3mxml/asconfigc/ASConfigCOptions.java

Line 34 in 62b8313

private static final String OPTION_UNPACKAGE_ANES = "unpackage-anes";

but didn't figure out how to use it (I guess it's maybe an extra argument to add in tasks.json). Copilot cannot figure it out either 😅

---

Can someone help me a bit on this?

Thanks in advance,
Aurélien

[joshtynjala]

ANEs are unpackaged by vscode-as3mxml for debug builds only. There is no option to enable unpackaging ANEs for release builds.

I found this option: unpackage-anes

This is an option on the asconfigc tool, which is the tool used to build a project based on the options in asconfig.json. By default, asconfigc doesn't unpackage ANEs, and this option asks it to. The option works only for debug builds, though. It will be ignored for release builds.

[Adolio]

Thanks Josh for your reply.

I'm wondering if this is a missing feature, a limitation or it is actually intended by design?

On my side, I commonly compile in release to test with ADL because my project just cannot run smoothly in debug. So right now I get the following error when trying to do a clean release build:

Error launching SWF debug session. Process exited with code: 5

Process terminated unexpectedly.

Error: Requested extension XXX could not be found.
The content cannot be loaded because there was a problem loading an extension: Error: Requested extension XXX could not be found.

In case you can't or don't want to add this in vscode-as3mxml, do you think that unpacking it in .as3mxml-unpackaged-anes via an external script during the build task could work?

[joshtynjala]

It was intended by design. However, in all my years of working on AIR apps, I've never worked on one that cannot run smoothly in debug. I've heard that debug builds can be a bit slower, but the slowdown has always seemed insignificant or undetectable in my experience.

In most cases, release builds should not unpackage ANEs, so I'm not sure the best way to make it an option.

do you think that unpacking it in .as3mxml-unpackaged-anes via an external script during the build task could work?

Yes, I think that would work. If vscode-swf-debug doesn't detect the .as3mxml-unpackaged-anes directory automatically, you can specify the directory in the extdir field of your launch.json configuration. Or, if you are running ADL manually, there is probably an ADL command line option to specify where to find unpackaged ANEs.