Hi Rob, I thought that was what you meant re InstallExecuteSequence :) Phil the sizes were nothing to worry about so that wasn't it.
In the end it looks like it was down to re-used Component ID or File ID's. I noticed that these were the same as in another package, and out of sheer desperation changed them - and it fixed the issue. As far as my understanding goes this had nothing to do with the error produced (or at least the error was misleading), but it worked in my case anyway. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Error-2902-Operation-ixfAssemblyCopy-called-out-of-sequence-tp7586131p7586171.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET Get 100% visibility into your production application - at no cost. Code-level diagnostics for performance bottlenecks with <2% overhead Download for free and get started troubleshooting in minutes. http://p.sf.net/sfu/appdyn_d2d_ap1 _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
