Archive: compile EXE with installation of main application?
compile EXE with installation of main application?
Dear Friends,
is it possible to compile an *.exe with the installation of the main application?
The idea behind is that my application installs several services which I want to uninstall at one time with a small exe.
Thx in advance
Chris
You can extract the executable to a temporary location (the plug-ins folder) and execute it.
Hmmm, think my question was not that clear Joost
I built an application with several services. Everything works fine with NSIS compiling it (FAT tool your NSIS :D).
So as I am developing several versions at once I would like to uninstall just the services (as they always have the same name in every version) at one time to install another version of the application. All services could be stopped with 'net stop <service>' and I could write a small application which is global valid (without pathes), but this won't work for un-installing the services.
My idea (or question?) was to take the installation routine, grep the installation path (from userinput, normally installation directory) for the services and bring them (the pathes) together in another application which is compiled during the installation routine.
The result should be a small exe with some
nsExec::Exec'"Path\to\service"-uninstall'
which could be executed to uninstall all services (just services) at one time.I think Joost was telling you, you could make an individual installer for each service and a main one. When the sselect what services they wnt in the main installer, it extracts the service installers to a temp folder and runs them.
Ah now....
(Had a hard day yesterday :igor: )
I understand, but that wouldn't be a distributable solution as all service binaries would blow up the installer about 20MB (extracted)...
Chris
What exactly is your question? Do you want your installer to compile another installer?
Why not create one uninstaller that can handle everything?
Great idea.
Yeah I thought of another installer (or uninstaller) compiled during installation of the application. So the output (the little exe) should be able to uninstall (only!) services installed with the main installation routine.
But the idea of using an uninstaller is great. Can I built two uninstaller? According to this topic a global one and one that *IS* the app I am looking for? This one should not self-delete...
Chris
Why not create a registry setting and let the uninstaller check the value and uninstall relevant components?
Because the uninstaller should be left untouched as it has to uninstall sometimes. And the little application I was talking off could be run several times (everytime I need it..)
:D
You can also use an uninstaller components page, then you can select what components to uninstall.