Thomas Heller wrote: > For example, the MSI which is currently built removes the file > associations when the package is removed, instead of restoring them to > their previous values. I have no idea how this can be fixed... This is a multi-step process. First, one has to find out how to restore associations in general, i.e. independently of MSI. Where should one store, on install, the information what the old association was? What if there already is "old" extension information? This is general Win32 stuff, and I don't know what the answer is. Then, how can this be integrated into an MSI file? Perhaps MSI already offers built-in mechanism for that, perhaps existing mechanisms for dealing with the registry have to be used. This is MSI specific, and is likely answered in the Microsoft MSI documentation. Then, finally, how can the Python script be changed to invoke the MSI mechanism? This is very easy: If you know what tables in MSI to manipulate in what way, the relevant Python code should become easily apparent. So in this case, I don't think any amount of documentation on the Python script will help to solve this problem (that is not to say that documentation should be avoided for this reason, of course). Regards, Martin
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4