Mike Dimmick wrote: > I still don't really understand why the Class table is being > de-emphasised. I suppose it's possible that if you advertise a Class - > say for a feature that is installed on first use - that that feature > will be installed if some third-party program references it, which could > surprise the user. > I think that's it, in general. With COM advertisement, you have no control over the user experience. MSI and COM are in control so you get "repairs" happening with basic UI at seemingly random times. With feature advertisement, there's generally a shell of some kind in control so you can (e.g.) plug in your own external UI handler. Plus it's generally in response to a particular user action, so there's less of the "huh?!" response.
There's also the potential for bugs, both in MSI/COM and in authoring. I know I've suffered more than once from "infinite repair mode." Rob would have more insight into the actual problems that pushed Office away from advertisement. -- 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
