DonationCoder.com Software > N.A.N.Y. 2015

.

<< < (9/9)

pillbug:
.

mouser:
The problem is that it's going to require the app dev to create the Inno setup exe and then run a little app I provide that will mark the Inno setup exe. At runtime, after determining it is being used within an Inno setup, the plugin will locate its process's parent process's exe file and then determine if that's the original setup exe. If so, the crap wrapping testing will proceed from that process upward, back to the shell or original launching app.
--- End quote ---

that's an interesting idea, but should be avoided if at all possible because of the extra work involved on behalf of developer..
the thing is, if that would work then surely an easier approach would work too, no? I mean if you can locate the inno setup exe then you can inspect it and check out its exe name and company info, and that will surely be able to tell you whether its INNO or not, no?

pillbug:
.

pillbug:
.

Navigation

[0] Message Index

[*] Previous page