那么原来的沙盒问题。不属于安装的一部分文件被放置在不同的安全沙箱中，并且因为它们位于不同的沙箱中，当导入父的孩子不继承其父在的ApplicationDomain 定义code>和两个独立的定义存在着哪些不兼容。可悲的是，似乎有解决这个的没有直接的方法。 Adobe却不允许通过 SandBoxBridge 沙箱之间的通信，但强迫你使用对象类型，哪一种违背了整个事情的目的。至于我可以告诉是没有办法的类在两个不同的沙箱中，即使他们是完全一样的是兼容的。我想它的后面不好受世界上没有严格的分型与对象。

Well it turns out its a Sandbox Issue. Files that are not part of the installer are placed in a different Security Sandbox, and since they reside in different sandboxes, the child when imported into the parent does not inherit the definitions of its Parent in the ApplicationDomain and two separate definitions exist which are incompatible. Sadly, there seems to be no direct way of resolving this. Adobe does allow communication between sandboxes via the SandBoxBridge, but that forces you to use Object type, which kind of defeats the purpose of the whole thing. As far as i can tell there is no way for classes in two different sandboxes to be compatible even though they are exactly the same. I guess its back the painfull world of no strict typing with Objects.