I have repackaged Macromedia Dreamweaver MX 2004 and was testing the application on the test machine. When the application is launched from the shortcut, it displays a few "Security Sandbox Violation" messages on the Falsh player debug console after which the application opens. I have gone through information on the Macromedia website about the new "sandbox" security feature part of version 6 and 7, but have not found a suitable fix for my problem. Although the test machine is part of the locked down environment, I do not suspect GP has any role to play in this, as performing a native install and launching the application does not bring up the error. Has anyone come across similar issues while repackaging this app?. Any pointers or solutions is highly appreciated.

0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


Hi Sri:

you have repackged Dreamweaver MX which is considered to be a complex installation since it registers many resource files at the runtime and has many custom actions associated with it. As you have repackaged the same the actions and registering of DLL's are not captured by WISE or whatever tool you have used to repackge it. Try doing the following:
1. Try to extract the Dreamweaver installation by right clicking on the installation and choosing Extract to here , probably you'll find the MSI within

2. Create a wrapper MSI that will call the dreamweaver setup in a silent mode.

Do let me know in case you need any help regarding the same.
Answered 08/24/2005 by: wiseapp
Second Degree Green Belt

Please log in to comment