Has no-one else had this problem that users can't click on shortcuts placed in
the start menu when the ALLUSERS property is set to 1? Maybe it is relevant but
this is happening on Windows 7 32-bit, I don't have an oppertunity to test how
this works on other platforms.
Kjartan
_
As I understand it, within a transaction you can only manipulate database
columns and rows that are marked "temporary" (because they don't exist in the
MSI itself) [see http://msdn.microsoft.com/library/aa367457.aspx]. So, instead
of removing rows, you will need to add them in the cases where y
Actually, the only difference between minor upgrades and small updates is
patch/transform applicability. UpgradeCode, the Upgrade table, the
FindRelatedProducts and RemoveExistingProducts actions are all
ignored/suppressed, and as a result ProductVersion is also ignored (except for
"assigning"
If two components must be always be installed/removed together, I don't see why
they can't be in all the same features.
If one of the components depends on another but the dependency is not mutual,
you could make a hidden feature that also contains the dependent component and
use a custom actio
I'm wondering where this requirement comes from. If the Native CA is
signed, why does it matter in an assembly that is stored inside of it is
signed or not? You can't tamper with the managed assembly without
invalidating the signature of the signed native assembly.
Either way, if you can't t
Hi -
We have managed custom actions in our setup. And now that we are getting
ready to ship - I have realised that we need to sign the managed dll and
pack that inside the native CA.dll. So far I have not had luck modifying
the wix.ca.targets file to split the build process into two parts to give
m
6 matches
Mail list logo
