Christopher, I appreciate your enthusiasm and advice.
> .NET is supposed to be XCopy deployment You are correct about this. If I take a clean machine (with .NET installed) and then 1. Install the IS original, 2. Install my WiX-produced version, 3. Copy both directories to a new clean machine (with .NET installed), 4. Run the IS-deployed program 5. Run the WiX-deployed program Both applications run identically. > But I'm guessing that your in the weeds right now in trying to figure out > what's "wrong" with the installer. I hope that I have not implied that WiX is broken. I'm assuming that in my WiX XML source code, I'm overlooking something simple, i.e. my ignorance is the source is the problem. I may be wrong, and be doing something odd that's obvious to somebody more experienced with installers (despite my attempts to approach the problem intelligently). I'm working with raw binaries from the build machine, with no source code on my WiX development machine. /All/ testing is done on a clean machine with .NET installed, separate from my development machine. However, I cannot ignore the fact that if I 1. Use a clean machine with .NET installed. 2. Perform the WiX install. The application will not work on that machine. The only case where the application fails to run is when I install with the MSI that I created with WiX. (As mentioned before, if I copy the directory to a new machine, it runs the same as the original IS-deployed application.) I'll continue digging, and try some of the things you suggested. ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
