Not a problem, The Windows Error Console confirmed my hunch. I now wish I could join my original message with the long stream so this makes sense in the future. In effect, you were having the installer look 3 levels deep into 2 non existent directories 1. The \ from the Pre-processor. 2. The \\ counted as 2 Additional Parent Directories. The 2 Parents Existed on your Dev Machine, but in essence the assembly you wanted installed didn't exist two levels up.
To see where the file exists in the MSI database look in the FILE Table of your old MSI using Orca. My guess is that the FILE Row for that GUID is blank. ----- The Birth and Growth of Science is the Death and Atrophy of Art. -- Unknown -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Re-WiX-Disaster-How-did-I-cause-it-tp7589302p7589321.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60133471&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
