Thank you, all, for the help. At this point I think I'm going to abandon WiX and bite the bullet and just rebuild my VS .Net 2005 dev environment. It's not my goal to fix the problems that exist within the Crystal merge module or wrestle WiX into submission and force it to deal with the mess... I just want to get something working to my client. Unless WiX can just shut up (yeah, yeah... it's not "correct", WiX. Get off yer high horse and do as you're told! :) and build the thing exactly as VS .Net does, I don't see a point in continuing down this path.
I've been in this game long enough to know that being technically and theoretically correct is something you contemplate while sipping sangria on a sunny beach somewhere with money you made from just getting stuff working ;P Believe me, a client will never care how many warnings or errors WiX gives and that VS hides if the package ends up working on their machine (which the previous VS installer did) What I find very odd about this, though, is that I worked for Crystal several moons (and mergers) ago and they had a very competent team working on the installers. I actually worked on the VS .Net 2005 integration (codenamed Granville to Microsoft's Whidbey) and I recall rigorous testing of the merge modules, or at least I THOUGHT that's what they were doing. I had no idea what going on over in their little corner, but I never imagined that they would pump out this kind of drek. I guess, though, their job was just to get it working within VS .Net so they didn't really pay attention to the technical "correctness" of the final product. It works very well within VS .Net (ummm... errr... I mean "very well" relative to all other Crystal products :) Thanks again! > Date: Mon, 4 May 2009 21:58:23 -0400 > From: b...@joyofsetup.com > To: wix-users@lists.sourceforge.net > Subject: Re: [WiX-users] Frustrated... can't get a simple installer to work > > Anthony F wrote: > > I'll be the first to admit that I'm by no means an expert in the art of > > creating install packages, but if VS can handle the messed up msm, > > shouldn't wix be able to as well? I thought (I may be WAY wrong on this) > > that the VS packager was based on wix? > > > > It is not based on WiX. And the packages you create with a flawed merge > module are flawed regardless of how you consume them. WiX is showing you > the errors, whereas .vdproj projects hide them. > > -- > sig://boB > http://joyofsetup.com/ > > > ------------------------------------------------------------------------------ > The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your > production scanning environment may not be a perfect world - but thanks to > Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 > Series Scanner you'll get full speed at 300 dpi even with all image > processing features enabled. http://p.sf.net/sfu/kodak-com > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users _________________________________________________________________ Create a cool, new character for your Windows Live™ Messenger. http://go.microsoft.com/?linkid=9656621 ------------------------------------------------------------------------------ The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
