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 think of a way to inject this into the wix.ca.targets ( I haven't looked myself ) then you can simpy choose not to use wix.ca.targets. After all, it's just some automation to call makesfxca.exe. You can switch back to standard charp.targets and then wire in your own postbuild events to sign the assembly and call makesfxca manually to create the native CA dll. ---------------------------------------- From: "Deepa Choundappan" <deepa...@gmail.com> Sent: Saturday, November 05, 2011 11:53 AM To: WiX-users@lists.sourceforge.net Subject: [WiX-users] Managed Custom Actions 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 me time to binplace correct signed managed dll's. Anyone else do this or have any other ideas as to how we can accomplish this. -- Regards Deepa ---------------------------------------------------------------------------- -- RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
