Christopher Brandt wrote: > heat.exe website WebPortal.2007.1.0 /out webportal.wxs > heat.exe website \WebPortal.2007.1.0 /out webportal.wxs > heat.exe website .\WebPortal.2007.1.0 /out webportal.wxs > heat.exe website localhost\WebPortal.2007.1.0 /out webportal.wxs > heat.exe website \localhost\WebPortal.2007.1.0 /out webportal.wxs > heat.exe website http:\\localhost\WebPortal.2007.1.0 /out webportal.wxs >
I don't know how the Web site harvesting works but have you tried /forward slashes/ instead of \backslashes\? > Finally, the Wix documentation hints that the development process > should include updating the .wxs file as new artifacts are added, > rather than trying harvest all of the changes at the end of the cycle. > Sounds great, kind of looks like Votive could help with this, but how > do we do it in practice? Make setup part of the development process. When someone adds a new resource (e.g., file), they add it to setup too. -- sig://boB http://bobs.org ------------------------------------------------------------------------- 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
