Saturday, February 7, 2004, 7:04:45 PM, you wrote:
> Right now, both the msi and msm tasks share some code, so some unnecessary
> things like this are present. I'll add those changes to the list of things
> todo with these tasks.
Sounds good.
> The TextStyle table can be removed. As for the binary table, the
> rows could be removed from it, but it should not be deleted as the
> user could still specify binary information for that table.
Yeah, sorry, I should have been more specific. Actually, it's
certainly possible to do dialogs in merge modules so as long as the
tables are empty and removed at the end, all's good.
> That data is left over from me just copying the MSITaskTemplate.msi
> file as a merge module.
Copy and paste inheritance.<g>
> As for the FeatureComponents table, the rows are populated because
> this table maps the merge modules components to the feature that the
> merge module is assigned to. The Feature_ guid
> {00000000-0000-0000-0000-000000000000} is basically a place holder
> to be replaced by the guid of the feature associated with the merge
> module.
But Feature_ refers to the Feature column of the Feature table; there
aren't GUIDs for features. (Which is weird -- there are GUIDs for just
about everything else in MSI.<g>)
Also, I'm pretty sure mergemod.dll uses the ModuleComponents table
when it's figuring out which components from merge modules should end
up in the MSI's FeatureComponents table. At least if you use
InstallShield or ActiveInstall, merge modules don't have a
ModuleComponents table...
--
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
