Hi folks,
I've recently had some issues where some features of my installers are being uninstalled unexpectedly.
So I have one "main" installer project which contains multiple features
Feature A
Feature B
Feature C (Windows Service)
Feature D (Windows Service)
This project is all set to up allow all of these features to be installed at the same time depending on which ones you choose.
I decided I'd like to also have 4 separate installers (one for each of these features so that if you only needed to install one of these you don't have to copy the main version around which is quite a big file)
The steps I took to do this were as follows:
1. I did a "save as" from the main project to create another version.
2. In the new version I would delete all of the features except for the one I needed for this installer. (Files/Folders, and Features from the organisation section)
3. I didn't bother deleting all of the dialog screens related to these components as they wont ever be initiated.
The issue occurred when I did the following on a local server:
1. Installed Feature A (using its seperate installer)
2. Installed Feature C (using its seperate installer)
3. Installed Feature D (using its seperate installer)
4. I then Uninstalled Feature A and it also removed the windows services from C and D. It didn't actually remove the files but it did remove the services themselves.
I think the reason for this was that although I had removed the features and files from the main project I hadnt removed the services from the services menu. (I just assumed they wouldn't have been affected as they were never installed in the first place from this installer anyway).
So my question is this, what is the safest way of creating smaller installers from a main installer without them being linked in any way.
I'm guessing changing the Product Name and Product IDs is one I'd need to do but is there anything else I should be aware of?
FOLLOW US
Get the latest news in Application Packaging