Do you find that the flash remoting code you developed using Flash MX doesn’t work with Flash MX 2004? If you do, you are not alone. The following explains why it is not working and how to make it work again.
Basically, the reason your code doesn’t work in Flash MX 2004 is because your code was written in ActionScript 1.0, but Flash MX 2004 is using ActionScript 2.0.
JRun installation includes some flash remoting samples. These samples seams to work with Flash MX and Flash MX 2004. Those samples were written in AS 1.0, how come they work with Flash MX 2004? The answer is because the samples included the compiled swf files. If you rename or delete the swf files, and try to compile those samples in Flash MX 2004, you will get compile error.
To make the code written in AS 1.0 to work with Flash 2004, you need to install âFlash Remoting Components ActionScript 1.0 for Flash MX 2004 and Flash MX Professional 2004â? FlashRemotingComponents-win-en.exe from
If you are writing new code, it is the best to write in AS2.
To use the AS2.0 version you, you need to download the flashremoting_comp_as20-win-en.exe from
then, there are couples of more things you need to do. I havenât tried this myself, but here seams to be the steps you need to do:
1. drag the RemotingClasses by doing the following:
From the open fla file in flash, go to Window — > Other Panels –> Common Libraries –> Remoting
Then drag the RemotingClasses on the stage of your movie. You can delete it off the stage and it will stay in your library.
The RemotingDebugClasses is for debugging during testing. You may want to remove this from your library when you go to production to reduce the file size.
2. You need to use
Instead of #include “NetServices.as” because it is deprecated.