Creating a package for Studio MX 2004
Hey guys
I am looking for some info on how to create a package for macromedia studio MX 2004 using wise package studio 4.5. The last package we made sorta worked but intermittantly tried to reinstall itself at various times all over the company. So I am looking for a procedure on how to create a package for it properly. Also has anyone got any ideas on how to distribute the updates. Do you need to install those in the initial package or create another package for these. BTW this is only my 3rd attempt at creating a package so am relatively new at this.
Any help would be very much appreciated.
I am looking for some info on how to create a package for macromedia studio MX 2004 using wise package studio 4.5. The last package we made sorta worked but intermittantly tried to reinstall itself at various times all over the company. So I am looking for a procedure on how to create a package for it properly. Also has anyone got any ideas on how to distribute the updates. Do you need to install those in the initial package or create another package for these. BTW this is only my 3rd attempt at creating a package so am relatively new at this.
Any help would be very much appreciated.
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
bkelly
20 years ago
The closest thing you are likely to find by way of documentation is probably here
As for the reinstallations, this is normally due to either package conflicts or the inclusion of elements in your package that do not belong.
For package conflicts, AdminStudio, Package Studio and Prism all provide conflict checking/resolution (if you buy the appropriate edition) which will help you ensure you do not have packages stepping on one another.
For garbage in your package, look for temp files, zero byte files in the file table, windows protected files, or personal files (like administrator profile components). Knowing what does not belong comes from personal experience/trial and error, or you can check out the new PackageCleaner product that identifies these kinds of things for you.
As for the reinstallations, this is normally due to either package conflicts or the inclusion of elements in your package that do not belong.
For package conflicts, AdminStudio, Package Studio and Prism all provide conflict checking/resolution (if you buy the appropriate edition) which will help you ensure you do not have packages stepping on one another.
For garbage in your package, look for temp files, zero byte files in the file table, windows protected files, or personal files (like administrator profile components). Knowing what does not belong comes from personal experience/trial and error, or you can check out the new PackageCleaner product that identifies these kinds of things for you.
Posted by:
PuterFix.biz
20 years ago
I recommend you remove anything that is destined for the AppData or LocalAppData folders. We found that if you left the 70MB worth of files in the Local AppData folder Flash MX would take upto 45 minutes to load for the first time. Also don't capture the flash play in your package because you will find that even just opening internet Explorer will cause the Studio MX package to install.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.