sWORDs's Posts

Three ways to reach that goal: 1) Create a vbscript that uses the windows installer object to edit the msi and add the dll to the file table. 2) Use WiX, use dark.exe to generate a xml (.wxs)... See more...
Three ways to reach that goal: 1) Create a vbscript that uses the windows installer object to edit the msi and add the dll to the file table. 2) Use WiX, use dark.exe to generate a xml (.wxs) and use fragments, then use heat to harvest the bin the directory and create your file fragment. 3) Add a custom action in the template.msi with Orca that copies the dll aswell when it exists.
Actually the productcode and upgradecode should not be equal between the two (excel and access are different products). And changing the guid manually shouldn't be an issue as long as it's uniqu... See more...
Actually the productcode and upgradecode should not be equal between the two (excel and access are different products). And changing the guid manually shouldn't be an issue as long as it's unique on that system. There are three guids in a msi: Package Code - To identify the package if even a bit of the msi changes so should the package code Product Code - To identify the product Upgrade Code - To identify a set of products (when upgrading you can use multiple upgrade codes to upgrade from) The error you're getting seems to be with the package code or in the upgrade table min version is not set (or is higher then the current version). Besides that your installer registry keys might be dirty, check the entries in HKCU and HKLM. You might have some leftovers with the same Product Code, or try to use a dirty machine/profile. And Peter, nice avatar, I can actually recognise you, Hilko (Apeldoorn, Netherlands)
I'm guessing you're trying to do the latest version. It actually uses IE to display powerpoint and I didn't manage to thinapp it successfully aswell.