Nicholas Muguira wrote: > I'm using a Votive Project in VS 2005, that uses a make file to > compile the wxs file.
Ah, well that would be why it works for you then ;-) The wix.targets is set up so that if you pass more than one .wxs file in the @(Compile) it errors out, as it is explicitly naming the output file with a .wixobj extension. I modified the wix.targets so that it will create a "candle.exe 1.wxs 2.wxs 3.wxs -out path" type command-line from a @(Compile) ItemGroup, and also will then transform the @(Compile) ItemGroup so that the correct .wixobjs are used in the light task. This enables the Build target to be used with multiple .wxs. I suppose an alternative would have been to ignore the Build target and call Compile once for each .wxs and then light them all together, but I like my approach more ;-) As you can see, I create an extremely simple msbuild file for the installer package: <?xml version="1.0" encoding="utf-8" ?> <Project xmlns="http://schemas.microsoft.com/developer/msbuild/2003"; DefaultTargets="Build"> <PropertyGroup> <OutputName>Testing</OutputName> <OutputType>Package</OutputType> <ToolPath>C:\Program Files\Windows Installer XML\bin</ToolPath> </PropertyGroup> <ItemGroup> <Compile Include="Configuration Database Installer\*.wxs" /> <WixLibrary Include="C:\Program Files\Windows Installer XML\bin\sca.wixlib" /> </ItemGroup> </Project> which can then be called by msbuild either from the command line or by Team Build with an MSBuild task. Mike ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ WiX-devs mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wix-devs
