Documentation is busted, oops. However, none of the standard heat arguments use a colon. The other things are extensions and are not part of heat. The colon was unusual compared to most of the other options. It doesn't help that light is confused (like -cultures <sigh/>).
Colons have been issues due to tab completion and I've heard PowerShell integration (I don't actually use PowerShell so that's all secondhand). Those reasons are why we've avoided the colon for most cases and instead use spaces (or no space). Thoughts? (documentation definitely needs to be fixed if it stays this way). -----Original Message----- From: Neil Sleightholm [mailto:[email protected]] Sent: Friday, January 23, 2009 10:49 To: [email protected] Subject: [WiX-devs] Heat change -indent One of my Heat changes was implemented slightly differently to how I did it. I implemented -indent:<n> but it was implemented -indent<n>, the reason I included the colon was to match WiXCop and some of the other Heat options (e.g. -t, -template and -pog) plus I think it is more legible. (The Heat documentation was also written to include the colon so would need revising.) Please could the colon be put back? Thanks Neil Neil Sleightholm X2 Systems Limited [email protected] ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ WiX-devs mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wix-devs ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ WiX-devs mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wix-devs
