views:

693

answers:

5

I'm just starting out with WiX as I need to be able to automate building an MSI on our CI server. Is there anyway to automatically include all the dependencies of a project?

A: 

In my experience, Wix is a still a very manual process. You have to add each dependency singly - I think the idea was that you would build the Wix installer at the same time you are building your project and add each item in as you are adding it in the code. This way it seems less daunting than having to go back and do a retrospect on the project. It certainly would be a great suggestion for an enhancement though!

silverbugg
+1  A: 

I haven't seen something in WIX that can do that, you are supposed to know all the dependencies that your solution/project requires. Read this blog, inside is a quote:

Keep your source close and your dependencies closer (apologies Sun-tzu.)

The best way I found to make sure nothing was forgotten in the MSI, was to test the Installer on a clean installed virtual PC.

The closest I've seen, for something you want is this guy's blog.

For now, we are stuck to do it by hand.

CheGueVerra
+3  A: 

The "proj" extension to heat.exe is getting better. Heat isn't quite ready to be used for production in an automated fashion. It's a very reasonable way to get the initial structure put together but doesn't quite do the right thing with repeated runs (for example, Component/@Guids aren't stable, yet...).

When the above issues are solved in heat.exe then incorporating it into your build process will certainly save all the trouble that people mention above. It's on our list to do better after the most egregious bugs are fixed in the core toolset.

Rob Mensching
Discovered heat about 10 minutes ago. Got the dependency list now, so I don't have to type it out. Looks promising :D
Chris Canal
A: 

I just started with WIX and think that WixEdit(http://wixedit.sourceforge.net/) rocks for adding multiple files/dlls, solved my frustration with Wix of getting the files in easily. Just keep your files organized and then use the import folder function. Of course it doesnt support the new 3.0 recommendations of having one component per file.

Heat is good also and supports one component per file. Next on my list is to get some automation so these files are updated automatically a la visual studio.

Brian
A: 

Have a look at paraffin.

Ivaylo Bratoev