Well, with some common sence i managed to find a fix for the cache problem i encountered while using classes in my flash movies, which are located on a networked drive.

As you can read in my previous post, Flash caches the Class files you use in a Flash movie. To fix this problem, here is a simple yet effective solution.

Try to get access to the PC which is the networked drive you are storing your classes on and make sure you set the system time of that PC ahead of the system time of the PC you are developing on.

Flash uses the timestamp of files to assertain if he has to update it’s cache. By setting the clock of the network server ahead, it will always update.

It’s not a very pretty solution, but it works.

Update: I came across a macromedia support article about this subject.

Update2: In the 7.2 update for Flash MX 2004, this issue is partially solved by adding a custom command to the program which should solve the problem temporarily until version 8 of flash is delivered.

While developing my first RIA, i ran into a freaky problem when using external class files which are located on a network drive, instead on my local drive.

It seemed flash caches the class files when compiling, and checks the timestamp of every class on compiling to see if it should get the latest version. When using a networked drive, these timestamps seem to get mixed up and scr%wed.

Macromedia identified this problem, but didn’t give a good solution for it. The only fix seems to be to store your class files locally :( (how lame can it get…)

So if you are editting classes and don’t see the desired results when testing your flash movies, think about this, it might be a cache problem. (WOohoo, back to our great dhtml days ;) )