nitzzzuanother question:
does the initial wyUpdate.exe + client.wyx change across updates as I saw in the tutorial that you build both wyUpdate and updates for each release.
wyBuild + Wix
nitzzzuHello,
We are planning to purchase wyBuild but first I need to make sure that it fits our deployment scenario.We are now having a clickonce deployed Wpf business app.
Since we hate clickonce so much, we are thinking to replace the current deployment with Wix (for initial setup) and wyBuild for deploying updates. What I don't understand it's what happens in the following scenario:
we have v1.0 installed through Wix. this will have an uninstaller. We issue the 1.1 update through wyBuild. The 1.1 update adds new files and also modifies current files. What happens when the user uninstalls the app from Add/remove programs? What happens with the new files added by wyBuild and not found in the uninstall manifest? Does wyBuild generate an uninstall? I want an experience similar to clickonce (without the bugs) 🙂Is it possible to create a Wix bootstrapper that will contain only the prerequisites + wyupdate. How will the uninstall behave in this case?
Thanks
nitzzzu
To uninstall newly added files, registry, etc. then call wyUpdate with the /uninstall flag.
Is it possible to create a Wix bootstrapper that will contain only the prerequisites + wyupdate. How will the uninstall behave in this case?
Yep, you can do that. In this case wyUpdate will behave like it normally does -- removing all files, registry, etc. that it added to the end-user's machine.
Does that make sense?
does the initial wyUpdate.exe + client.wyx change across updates as I saw in the tutorial that you build both wyUpdate and updates for each release.
Well, the client.wyc might change depending on what you change in your wyBuild project. You should*never* include wyUpdate.exe in your update. However, if you're building new bootstrapper msi file then, yes, rebuild wyUpdate.exe and include it in your latest installer.