How do you install custom CS extensions in Flash Pro CC for testing and debugging before they have been signed and packaged?
We have a custom extension for Flash Pro developed in-house using the CS SDK that we've been using with flash pro CS5 and CS6 but we're having trouble getting it to work in CC and I'd like to run it locally in test/debug mode.
With flash pro CS6 and CS5 it was possible to test extensions by copying the output folder from flash builder into the CS Service Manager root folder (e.g. /Users/<username>/Library/Application Support/Adobe/CS6ServiceManager) and setting PlayerDebugMode to 1 in the CSXS preferences.
I've added the PlayerDebugMode=1 flag to com.adobe.CSXS.4.plist however, I can't find the equivalent service manager folder for Flash Pro CC to copy the extension into.
Is there a different folder to use for CC or is the process for testing extensions completely different? (are extensions written in the CS SDK even compatible with CC?)
I'm running Mac OS Lion.
Hi Stephen, CSXS extensions are dropped from Hellcat. You can use the SWF/JSFL extensions that is mentioned in the extensibility document
Thanks, that explains a lot.
I'm afraid I'm a bit confused about what the preferred way of developing extensions is going ahead. There seems to be a lot of conflicting documentation on the adobe site, e.g. http://www.adobe.com/devnet/creativesuite.html seems like the top page for extension documentation but it only talks about CS SDK 2.0 which uses CSXS and doesn't seem to be compatible with creative cloud apps.
Then there's CS Extension Builder 2.1 which looks like it supports Flash Pro CC but isn't mentioned in the pages you linked too and it doesn't mention JSFL, but talks about the CSAW library.
Do you know if:
* The CS SDK has been dropped completely?
* CS Extenstion Builder is deprecated? (I can't see it as an option in the list of Creative Cloud apps)
* Is then any documentation/utilities to help migrate existing CSXS extensions to work with creative cloud apps?