Manage multiple projects in the same workspace

[PippoApps]

Hello there,
what would you consider the best way to manage multiple projects within the same asconfig.json?
Use cases:

• Multiple projects using the same codebase with diverse project class extensions
• Shared code between several machines where AIR path is not the same
• Using different FLA files to compile in animate

So far I store several asconfig.json files in different folders and just overwrite the current one.

Any suggestion for a smarter method?
Cheers

[joshtynjala]

where AIR path is not the same

Where the SDK is located shouldn't affect the contents of asconfig.json. If you are referencing absolute paths from your SDK in your asconfig.json, try switching to using the ${flexlib} token instead. It references the frameworks directory inside the SDK. This is actually a feature provided by the AS3 compiler, so you can even use ${flexlib} on the command line when using mxmlc directly. Example:

"library-path": [
    "${flexlib}/libs/sdk_lib.swc"
]

Any suggestion for a smarter method?

Instead of overwriting a file, you might consider using the extends field in asconfig.json to reference another asconfig file.

https://github.com/BowlerHatLLC/vscode-as3mxml/wiki/asconfig.json#extends

So you'd keep your multiple asconfig files for your various configurations, but you could have one main asconfig.json file where you simply change the path when needed.

{
	"extends": "./asconfig.other.json"
}

---

Personally, here's how I'd probably organize a project like this: I'd put each asconfig file in a separate directory, and treat them each as separate projects. Then, I'd use the source-path compiler option to reference any code that is shared by all of them. I might also use a multi-root workspace to add each of these projects to VSCode in the same window.

[PippoApps]

Thank you Josh,
I had missed the "extends" feature; that's precisely what I need.