External Actionscript Classes Version Conflict

[Flash Gordon]

Scenario:

• swf B compiles with class Vo in it and displays it's values
• swf A compiles with a revised version of Vo in it and loads swf B

Result:
swf B shows swf A's revised Vo class properties and not the version it got compiled with even though nobody told swf B to change it's Vo properties.

Has anyone encountered these kinds of situations? How is everyone dealing with this?

[EDIT] Since the forums still seem to be broke, you can grab my sample files here. Compile B.fla and then change class Vo version property and you'll see when you compile A that B display's the new Vo version. Link to Files

[Tilpo]

I don't really know what you mean, but often when changing files that are already uploaded people can use xml to alter the data inside, or simply replace the file. What do you mean? Please specify!

[Flash Gordon]

no. I'm talking about ApplicationDomain issues.

[maskedMan]

I've encountered this many times. Usually we only recompile swf B if some aspect of the new version of the class file residing in swf A causes things to break.

Sometimes you can use this behavior to your advantage, though. For example, if you know that changes to class Vo must be made across the board, but that no interactions with Vo must be changed in the B level swfs, all you would need to do is compile the changes into A and then not worry about the loaded children... at least not until you are forced to have them stand alone.

[Flash Gordon]

Yea, it looks like there is no way around my problem. I could "partition" the swf by loading B into a new ApplicationDomain() and then that behavior won't happen, but then I can't type B to IB anymore: I lose my interfaces. Sigh.....I don't know if it's a limit of my knowledge of domains or if it is just the way it is. Follow me?