>OK, I'll try to put the ocx's in a separate library instead of with the main executable.
>
>I'm curious of the way you distribute VFP runtimes. I was tempted to pack the runtimes files also but, as we distribute DLLs that can be called from other apps as COM+ objects (Ex. from Excel, VB, .NET), I guess we have to leave the runtimes unpacked, right?
I distribute them as separate files, not encrypted and not shrinked. Three reasons:
1) There's no need to encrypt them, since they're not part of my proprietary source.
2) They will shrink, but that's also done by Innosetup or any other setup application. And I don't mind that they have the original size on the user's machine. Moreover, on startup of the application no time needs to be spent (each time again) on unshrinking.
3) Updates only seldom require an update of the runtime files. Therefore, updates can be kept smaller.
Files that are not encrypted and not shrinked, need not be handled by Molebox. Simple as that.
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.
