Ward, Mike (MED US) wrote: > I think it pretty natural for someone to think the shortcuts would be > associated with the files here, not the component.
Generally, that's true, but not with advertised shortcuts. > I think some of this is just result of laziness. I didn't see a reason > to put the files in separate components because they always get > installed together. Components are *the* atomic unit in MSI so generally they should be as small as possible. That helps not only in this case but when it comes to patching and upgrades. > capitalized. Again, my understanding is limited but I think the compiler > might be able to help here. It appears a public property is one that can > be set at runtime. It's not apparent to me that a property used in a > RadioButtonGroup can ever be useful unless it's public. Perhaps there is > a use case I'm not thinking of here? > It's perfectly legal to use a UI construct only in the UI sequence. Where something is outright illegal or almost certainly won't do what the user intended, the compiler often emits a warning or error. For example, a Feature element's ConfigurableDirectory attribute is only useful with public properties, so if you try to use a private property, the compiler gives an error. -- sig://boB http://joyofsetup.com/ ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
