Re: Note: Issues with Runtime distribution and demos
Hi Chet,
Jeff pointed me to this and I think you raise a very good point.
I'm also glad that I'm not the only paranoid dev who looks for quirky ways to circumvent things.
Just a quick thought, I saw a post from, (I believe Dave M) suggestiing that command line args can be included in a vb.exe wrapper - which seems like a very good idea.
So..., can vb.exe propogate or create the runtime.exe on app load and destroy it immediately after?
For example, user clicks on exe that is essentially a vb wrapper for the launch & startup commands, also copying [whateverfilename] to 'runtime.exe' prior to running the app start. So, you would ship the vb.exe, along with [whateverfilename] - renamed runtime.exe when vb.exe is launched.
I'm treating this more as a logic/thought experiment than any effective test but seems that, unless runtime.exe must reside on disk, once the rt.exe is loaded into mem to run the app, it's physical presence is no longer required.
If this is true, and I'll test for it once I download and install A5, then runtime.exe can be called anything within the ship files, and only created/destroyed on app load. This avoids the problem of any user just starting runtime.exe (because it doesn't exist) and seeing the RT lic key via the about screen.
Thinking further, the vb.exe wrapper could write the runtime license key to the registry, copy whateverfilename to runtime.exe, launch the app, kill runtime.exe (if allowed), kill/rename the license # in the registry.
Should all happen before a use could interrupt....
But, just a thought.
Regards,
Gary
Hi Chet,
Jeff pointed me to this and I think you raise a very good point.
I'm also glad that I'm not the only paranoid dev who looks for quirky ways to circumvent things.
Just a quick thought, I saw a post from, (I believe Dave M) suggestiing that command line args can be included in a vb.exe wrapper - which seems like a very good idea.
So..., can vb.exe propogate or create the runtime.exe on app load and destroy it immediately after?
For example, user clicks on exe that is essentially a vb wrapper for the launch & startup commands, also copying [whateverfilename] to 'runtime.exe' prior to running the app start. So, you would ship the vb.exe, along with [whateverfilename] - renamed runtime.exe when vb.exe is launched.
I'm treating this more as a logic/thought experiment than any effective test but seems that, unless runtime.exe must reside on disk, once the rt.exe is loaded into mem to run the app, it's physical presence is no longer required.
If this is true, and I'll test for it once I download and install A5, then runtime.exe can be called anything within the ship files, and only created/destroyed on app load. This avoids the problem of any user just starting runtime.exe (because it doesn't exist) and seeing the RT lic key via the about screen.
Thinking further, the vb.exe wrapper could write the runtime license key to the registry, copy whateverfilename to runtime.exe, launch the app, kill runtime.exe (if allowed), kill/rename the license # in the registry.
Should all happen before a use could interrupt....
But, just a thought.
Regards,
Gary
Comment