> I'm not sure what other people think about this, but I usually prefer > to place my installing code in the application that is being > installed, and not have a separate installer.
The problem with this method is that unless you're logged on as an Administrator account, you may not have permission to write anything to the local hard drive's program files folder. Installers often ask for an administrator's account and password, thereby permitting the user to put things where they would otherwise be blocked. This issue is most common on Windows, but it can also come up with Mac OSX, too. I discovered it the hard way some years ago when a customer of mine at UC Berkeley found that he couldn't install my software and had to wait a month until an IT person could get there to do it...:( - John _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives of this list here: <http://support.realsoftware.com/listarchives/lists.html>
