1 person found this helpful
While you're having fun with ZXPSignCmd, also consider PlayerDebugMode to run them unsigned. Details are mentioned in Adobe Creative Suite SDK. I have no idea whether that still works, I just remember having seen that flag ages ago.
That does not seem to be helping. Should I remove the META-INF\Signature.xml?
Maybe it has to be placed manually in the same folder that the old Extension Builder would place debug versions in? And what folder would that be?
sorry, I haven't personally used ExtensionBuilder since around PatchPanel / CS4 - completely returned to plugins, and also for now skipped CEP.
I just retried the link, it opened in the front page of the bundle. Have you found PlayerDebugMode discussed within Programmer's Guide >> Debugging? I'm afraid I can't help beyond that.
Regarding signing the extension you probably need a old version of the ZXPSignCmd the signing process is quite simple.
You do not need to remove the META folder it will be regenerated on resigning or ignored if debug mode set to false
Trevor, this thread is about CS5.5 Flex extensions but cross posting won't hurt in such edge cases.
mlavie, as an afterthought: have you checked that the root certificate backing your new signing certificate is supported by your testing and deployment machines?
Dirk, when I set up that forum I deliberately included the terms CEP, Extensions and Add-ons as a felt that one of those terms should stay relevant for some time even given modern tendencies of changing names, methods etc. That's why you won't find the term HTML on the forum.
So now you know!