So, I was able to overcome the Assembly load error by reinstalling the properly signed 3.6 beta binaries and then only overwriting the select DLL/target files which contained the changes I made. (I build my installers as a non-admin, and test them on isolated virgin virtual machines.)
As to the multi-instance installer, I did create a fork with my changes and submitted a pull request. I assume this is the proper process, but I would like to follow up and do any additional leg work to get it into the main WiX source tree as soon as possible. If Bob or Rob has some free time, I'd really appreciate it if they could take a peek at my change (it really is a rather small one) and provide some feedback. Thanks, Jacob -----Original Message----- From: Bob Arnson [mailto:b...@joyofsetup.com] Sent: Wednesday, November 23, 2011 10:04 PM To: wix-devs@lists.sourceforge.net Subject: Re: [WiX-devs] Best approach formulti-instanceinstallers. On 10-Nov-11 15:45, Hoover, Jacob wrote: > Anyone care to comment? Is the developers mailing list always this > quiet/inactive? Mostly.<g> Multi-instance packages aren't terribly common, even in the tiny subset of folks who write installers, and the tinier subset of folks who write installer tools.<g> > I'm also not certain if it's possible to have multiple UpgradeCode's in > the Upgrade table, but I have accounted for it. It is. > Now my problem is with testing. As far as I can tell, my transforms are > fully functional but I run into another issue which is caused by me > having a custom compile of Wix on my machine (Failed to load assembly > Microsoft.Deployment.WindowsInstaller. Error code 0x8013141A). Doing > some background shows that this is caused from a difference in signed > assemblies (I assume the ones I build are delay signed, so they would > only function locally.) General rule is that if you can't mix and match "retail" WiX with bits from a local build. But you should be able to run everything from a local build. As long as you run the build once elevated, the build installs skip-verification entries for locally-build WiX assemblies. -- sig://boB http://joyofsetup.com/ ------------------------------------------------------------------------ ------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ WiX-devs mailing list WiX-devs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-devs ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ WiX-devs mailing list WiX-devs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-devs
