Hello Team Caphyon,
Learning more about your product each time we use it and try something different or test it out with different situation. Really a great product.
Wondering if you could offer suggestions with our situation. We are trying to minimize downloading for Updating existing applications. I have a pretty good understand of the differences with upgrades and patches. Patches are great. When we do updates that involve uninstall and reinstall I think our msi are overly fat because we were including dot net 4.0. Obviously if the client has our software installed ... there is no need to have dot net 4.0 when considering updating and patching. Patching totally removed the dot net .. however upgrades would include it.
Originally we were not creating an EXE setup file (Media - Bootstrapper tab) and our setup.msi were 94 megs. You must have changed something with the Bootstrapper as now in version 9.01 if we use this option ... and select leave install files outside; the prerequisite for dot net are also not included in the msi either (we use the dotNetFx40_Full_x86_x64.exe).
This was extremely good news as it has reduced the size of our Setup.msi to 43 megs (without the 49 megs for the dotNetFx40_Full_x86_x64.exe). (note file sizes are approximate).
My question is this ...
Our application also uses a third party library. This Library is approximately 75% of the application size (without dot net 4.0). This Library will not change that frequently. It is not an issue with patches as it is effectively removed for patches. However, for updates it would be part of the msi.
These libraries may change over time .. however likely our application would change more frequently.
Is there a scheme by which we can separate out this third party library and then only update it when required?
The library is to be installed in the same folder as the application, in a separate subfolder however:
3rd party library
These are just dlls that are localized for our application use only. Not putting them in Windows System32 folder or registering them for system use.
I am thinking:
4.0.0 Install with Library and dot net 4.0
patch to 4.0.1
patch to 4.0.2
patch to 4.0.3
upgrade to 4.1.0 (library has not changed)
patch to 4.1.1
patch to 4.1.2
patch to 4.1.8
upgrade to 4.2.0 (with new library)
and so on
Any help you could offer would be greatly appreciated.