ExtendedKey/Video class compile time issues in Adobe CS3 when working with Flash Lite 2.x content
July 2nd, 2007 by Scott Janousek
(No Ratings Yet)
Loading ...Overview
For anyone doing Flash Lite 2.x development with Adobe Creative Suite 3 you may run into a situation when you receive a compile time “class not found” type error when using the Flash CS3 ExtendedKey or Video classes … even though your syntax may be correct!
Here are some examples of the compile time “errors” in action:
Video class “error”:
Extended Key “error”:
This error can assume many forms, but some common ones are: “There is no property with the name ‘ExtendedKey’” or “The class or interface ‘ExtendedKey’ could not be loaded” as noted above.
Problem
Due to some (apparently) missing classes within CS3, this can happen when you are using this functionality outside of the Flash timeline, within a class based application architecture.
This has been already unofficially documented, and the manual steps to resolve this have existed (if one was savvy enough to search) for some time. I am revisiting this issue due to a specific community request.
Updated (Temporary) Solution
However, until, a Flash CS3 update appears, I have constructed an unofficial MXP that applies the steps above in a more automated fashion.
The MXP will copy the (potentially missing) ExtendedKey (ExtendedKey.as) and Device Video (Video.as) classes into the correct class path for CS3.
You should really only apply this MXP patch if you running CS3 and run into this specific issue and those still working with Flash 8 should not have to apply this at all.
Prerequisites:
Installation Instructions:
|
MXP (v1.0.0) (for both Mac and Windows):
(right click and save-as to download)
|
NOTE:
You shouldn’t have to exit out of CS3 for the fix to take affect … however it doesn’t hurt and Flash may instruct you to do so. |
Please let me know if you find other classes which need to be included in this MXP as well. In addition, all comments, feedback, etc can be feed to me.
Print This Post
July 2nd, 2007 at 3:29 am
Thanks for documenting this and providing a workaround, Scott. Very valuable
July 2nd, 2007 at 3:46 am
Hey Aral, no problem.
It is an annoying problem and is starting to surface more often now that CS3 has been adopted.
I imagine there will be a cumulative Flash CS3 update soon that addresses this specific item, but for now, I think this will do.
July 8th, 2007 at 8:48 pm
Yep… it’s a known problem by Adobe, though.
July 12th, 2007 at 4:39 am
[...] amigo del desarrollador (y en general de todo el mundo XD), como no, dimos con Scott Janousek, que detalla perfectamente en un post el problema y por si fuera poco, ha preparado una extensión para solucionar al menos de momento el problema, [...]