6776
Living Room / Re: Programming/Coder humor
« Last post by mouser on December 26, 2014, 12:50 AM »
Recent Posts
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.
But there are no identifiable versions of not only the app I told it to install but also the crap-wrapped plugin dll and the setup script. Apparently those are still packed up and thus inaccessible by the plugin.
Given all that, I'm at a loss as to how to tag the exe running the plugin dll as 'okay', given that its parent is another Inno Setup process/executable, giving it all the markers of being crap wrapped.
Special holiday greetings to Nudone, the father of Cody and the one who breathed life into him by drawing his picture.
My gut feeling tells me the safest, last resort, way to approach this sort of issue is to prompt the user for the installer file used, compare that with what the system says your installer's exe path is, and proceed accordingly.