Sometimes, when we install a product, the environment does not meet all the necessary criteria and some step from the installation process crushes. What happens with the changes made by the previous steps that completed successfully? How can the installer undo those changes?
- doc/article/README.md
- This document contains a step-by-step tutorial. You can find there additional explanations on the described problem and steps to solve it.
- I suggest to read this tutorial in parallel with the code.
- sources
- I provided the complete Visual Studio solution that solves the described problem. Use it if you need to test it by yourself, in your environment or if you have further ideas that you want to verify.
- A shorter version of the tutorial can be found directly in the source code.
- Open Visual Studio solution
- Search (Ctrl+Shift+F) for the
STARTcomment. It usually can be found in theProduct.wxsfile, but it is not a rule. - Then follow the
Stepcomments in the numbered order.
- Note: The
NEXTtags at the end of each comment indicates the file where to search for the nextStep.
- doc/logs
- Sometimes a quick look into the log files may be useful, but running the installer each time is cumbersome. I generated the log files for the meaningful scenarios and I placed them into this directory. Have a look when needed.
Fill free to use the discussions page whenever needed:
- Do you have an improvement suggestion?
- Is there any typo in the articles or bug in the code?
- I appreciate any information on how you used this tutorial and if it was useful to you or not.
- Do you have any other questions?
If you like my work and want to support me, you can buy me a coffee:
