Saturday, February 7, 2004, 5:04:28 PM, you wrote: > You need to add these properties to the build file. The values specified > are just examples and can be changed:
Excellent -- that did the trick! I'm curious, though; there isn't an MSI requirement that merge modules have those properties, so why does <msm>? They'll never get into a final .msi unless the .msi itself didn't have them set. The resulting .msm is mostly perfect. A couple questions: - <msm> populated the FeatureComponents table, which doesn't make much sense for a merge module. - MSMTaskTemplate.msm includes the Binary and TextStyle tables. Again, that's not typical use of a merge module. Is there a way to remove arbitrary tables (like how it currently removes empty tables)? -- sig://boB http://foobob.com ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ NAntContrib-Developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nantcontrib-developer
