>Hi Peter,
>
>>Yes, this is one possibility, but you can also distribute them together with the application by putting copies in the application's folder. This is what I prefer personally.
>
>I'm happy to speak with you on the topic of Molebox since I too am a big fan of this product.
>
>I can understand why you ship your VFP runtimes seperately.
>
>As for me, I like binding the VFP runtimes into my main Molebox EXE because I'm paranoid that users may mistakenly delete or overwrite runtime files stored seperately on disk. I also enjoy the convenience of having a "single file" main EXE to distribute.
>
>Let's continue to speak up about this (Molebox) great product!
I hope your users don't delete your main exe. :)
Inclusion is fine and legitimate, of course. But the drawback may be that updates always have to include these megamonsters. And I don't see a gain in encrypting these MS-proprietary files. Also, compressing is not my motive for using Molebox, because Innosetup does compress also. Moreover, compressing would imply that they have to be decompressed on every start of a session.
Groet,
Peter de Valença
Constructive frustration is the breeding ground of genius.
If there’s no willingness to moderate for the sake of good debate, then I have no willingness to debate at all.
Let's develop superb standards that will end the holy wars.
"There are three types of people: Alphas and Betas", said the beta decisively.
If you find this message rude or offensive or stupid, please take a step away from the keyboard and try to think calmly about an eventual a possible alternative explanation of my message.