Olaf Doschke
Programmer
This is not meant as a joke: I'd set up such an app store (literally including VFP .APPs) , I am done with the core concept already, I developed quite a simple concept for myself to install and update foxpro applications into a users C:\Users\USERNAME\AppData\Local\Apps\ folder, like ClickOnce does.
Reasoning:
1. As clickonce does it, too, that can't be too wrong.
2. I can much easier update files in that folder, than in \Program Files\, it doesn't need elevated access.
2. In regard of security: I know Clickonce requires you to sign your application, so do I.
3. The only classic install remaining once is a updateandstart Executable users would need to install comparable to Apples iTunes.
I really put APPs in there, you only need to specify some startup code, in the simplest case DO your.app in configuration files (which themselves are signed).
I would - even just for the fun of it, and this is where it also could be halfways a joke - develop a webstore for VFP apps on top of this core concept, though it's a dying species and the typical VFP application is not an app in the modern sense of the word. VFP was just too early with it's APP extension :^).
I know there already are fine articles on using clickonce itself to update your app, Craig S. Boyd has also written a small updater routine for you to use for free, then there is THOR for the VFPX projects and IDE extensions, and within customer sites I myself simply use xcopy and robocopy, no need for going out to a website to download updates.
But what about leveraging synergy effects this may have? Let it only be a trusted site for VFP applications, it doesn't have to be standalone, could lower the individual costs and security efforts and also hold as a license server. And if enough developers join this also will have an advertising effect.
Would you use such a shop for your application?
Under which conditions?
Which features would you like?
Bye, Olaf.
Reasoning:
1. As clickonce does it, too, that can't be too wrong.
2. I can much easier update files in that folder, than in \Program Files\, it doesn't need elevated access.
2. In regard of security: I know Clickonce requires you to sign your application, so do I.
3. The only classic install remaining once is a updateandstart Executable users would need to install comparable to Apples iTunes.
I really put APPs in there, you only need to specify some startup code, in the simplest case DO your.app in configuration files (which themselves are signed).
I would - even just for the fun of it, and this is where it also could be halfways a joke - develop a webstore for VFP apps on top of this core concept, though it's a dying species and the typical VFP application is not an app in the modern sense of the word. VFP was just too early with it's APP extension :^).
I know there already are fine articles on using clickonce itself to update your app, Craig S. Boyd has also written a small updater routine for you to use for free, then there is THOR for the VFPX projects and IDE extensions, and within customer sites I myself simply use xcopy and robocopy, no need for going out to a website to download updates.
But what about leveraging synergy effects this may have? Let it only be a trusted site for VFP applications, it doesn't have to be standalone, could lower the individual costs and security efforts and also hold as a license server. And if enough developers join this also will have an advertising effect.
Would you use such a shop for your application?
Under which conditions?
Which features would you like?
Bye, Olaf.