The Mallow utility I use generates new GUID's for the components each time, and this is okay with us. Our installers are 100% internal, all-or-none kinds of things. No patches, no upgrade codes, etc. They're mostly internal web services that are only installed or seen by our IT guys, so I know we do some 'sloppy-ish' things with them that violate all kinds of ICE checks.
That being said, here's the script. It's probably a bit specific to what we do, but there should be some good ideas in there for other folks. Also, I don't proclaim to be a Perl guru, but I try to write a lot of comments. The script is very Visual Studio centric. The first argument is the path to a VS2003 project file, or a top-level directory you want to import into a fragment (for VS2005.) The second argument is the platform/style of file tree you want in your installer: 2003: VS2003 web style - Finds content files, puts binaries in bin directory. 2003_flat: VS2003 app style - Finds content, mixes binaries in with them at top level. 2005: VS2005 style - just sucks in a whole directory. The mallow.exe utility (which I can't find online any more?) spits out Wix 2 fragments, though we've moved on to Wix 3. So I have a lot of code in there that schmoozes it. I plan on moving over to Tallow at some point but I haven't gotten around to it yet. There is also some logic in there to check the generated fragment file into Perforce if new files have showed up, or if files have been deleted. What you end up with is a fragment called FileList.wxs that you have to compile and link into your main installer. It creates one big component group that you can include, and by default stages everything under INSTALLDIR. I've rambled on long enough. Feel free to send questions my way if you're curious about anything or can't get it to work. BTW, open source is implied; use, copy, pillage to your heart's content. -Matt _____ From: Rob Mensching [mailto:[EMAIL PROTECTED] Sent: Thursday, March 08, 2007 8:28 AM To: Kerry, Matt; Matthew Janulewicz; wix-users@lists.sourceforge.net Subject: RE: Re: [WiX-users] Tips for deploying a Web app as an MSI Matt, How do you keep the Component/@Guids stable from scan to scan? From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kerry, Matt Sent: Thursday, March 08, 2007 2:15 AM To: Matthew Janulewicz; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Tips for deploying a Web app as an MSI Yes, I would be very grateful if you could send me the script. It sounds like you are successfully doing exactly what I';m trying to achieve. Matt _____ From: Matthew Janulewicz [mailto:[EMAIL PROTECTED] Sent: 07 March 2007 18:14 To: Kerry, Matt; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] Tips for deploying a Web app as an MSI At installer compile time, each file has to be named explicitly. I've written a Wix build script (and use some custom commands in Visual Studio, but that really doesn't matter) that uses a utility called Mallow to build the source tree that gets included in our installers. For what it's worth, I separate the INSTALLDIR tree into a different file then link the two together. The file list in our installers changes constantly, and the rest of the UI etc. doesn't so I keep them separate. If you're interested in looking at my script let me know and I can send it to the list. -Matt _____ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kerry, Matt Sent: Wednesday, March 07, 2007 7:54 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Tips for deploying a Web app as an MSI I am looking to create an MSI in order to deploy a Web app to our production servers. We already have a build process in place using VisualBuild, that we would like to keep and I have got all the virtual directory, app pool etc. creation and properties working beautifully - which I thought would be the hard bit! How I'm just looking for some tips as to how to wrap up all the files. As it is a Web app there are loads of aspx, js, html etc files plus a few dlls. Is there a clever way to include all the files for an app in the wsx file, without hardcoding them. Any tips greatly received. Matt Visit our website at http://www.halcrow.com <http://www.halcrow.com/> ------------------------------------------------------------------------ The contents of this email are confidential, for the sole use of the intended recipient at the email address to which it has been addressed and do not give rise to any binding legal obligation upon Halcrow companies unless subsequently confirmed on headed business notepaper sent by fax, letter or as an email attachment. Whilst reasonable care has been taken to avoid virus transmission, no responsibility for viruses is taken and it is your responsibility to carry out such checks as you feel appropriate. Emails supplied are as found and there's no guarantee that the messages contained within the body of the email have not been edited after receipt. If you receive this email in error, please contact the sender immediately and delete the message from your system. Thank you. Halcrow Group Limited. Registered office: Vineyard House, 44 Brook Green London, W6 7BY. Registered in England and Wales, Number 3415971. ------------------------------------------------------------------------ - Click here <https://www.mailcontrol.com/sr/wQw0zmjPoHdJTZGyOCrrhg==> to report this email as spam.
WixContentGenerator.zip.rename
Description: WixContentGenerator.zip.rename
------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
