Chronology
- Our product was targeted to .NET2.0, now it has changed to .NET4.0,
- Customer is unhappy and wants us to install .NET4.0 along with our app (yes, it is kind of strange),
- Installation is OK (wix bundles), but we have an upgrade process for customers in place:
- It checks whether customer wasn't upgraded to newer software version meanwhile,
- If it was, then self extracting binary is downloaded & extracted, iteffectively replaces the old binaries.
Solution
- During extraction process I have a possibility to run .NET2.0 targeted exe coming from within the self extracting binary,
- I decided to embed the .NET4.0 web installer (due to its small size) directly into this .NET2.0 targeted exe and to run it once I find out .NET4.0 is not installed (based on registry).
People above me unfortunately have concerns about "what if .NET4.0 web installer will stop working?". They are worried that the URL which this installer is internally using to download the full installer may change and web installer will become useless in such case. Are their concerns legit? Is anybody aware of similar situation happening in the past?
EDIT: Faulty internet connection is not of concern here, that is something I can live with, the question stands whether i can expect .NET web installer to keep working for decent amount of time (I will embed the web installer today, but what if customer upgrades to newer version of our software after 1 year, will web installer still be valid?).