Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I created a windows Installer MSI package that installs assembly binaries (exe) with their libraries (dll), each set with their own keyfiles. When I delete an assembly binary or a resource files, it does not trigger a repair? The same installer with Win32 binary and resource files repairs everytime?
Repair and Resilency have slightly different meanings. Repair is invoked ( like through Add/Remove Programs ) and Resilency is triggered.
Common triggers for resilency are advertised shortcuts and COM activation. When resilency is triggered, it will invoke a repair on the entire primary feature that the corrupt component belongs to.
Since your .NET, it’s unlikely you are using COM. Use an Advertised shortcut for the EXE and put all of the components in the same feature. If this doesn’t work, there are also ways of calling the MSI API via an interop library in your code to perform your own custom health check and invoke repair.