Feature Requests item #1115450, was opened at 2005-02-03 06:35 Message generated for change (Comment added) made by derekc You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=642717&aid=1115450&group_id=105970
Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: harvester (heat) >Group: Next Release (example) >Status: Pending Priority: 3 Submitted By: anfortas (anfortas) Assigned to: Derek (derekc) Summary: Support harvesting of type libraries Initial Comment: Nearly all the TypeLib attributes, such as Language and MajorVersion, as well as contained interfaces for the non-advertised case, could easily be programmatically obtained from the type library itself automatically. When TypeLib is under File, let this data be automatically inferred from the file. ---------------------------------------------------------------------- >Comment By: Derek (derekc) Date: 2006-07-25 23:59 Message: Logged In: YES user_id=518766 heat now support harvesting of type libraries, enjoy :) ---------------------------------------------------------------------- Comment By: Derek (derekc) Date: 2006-07-24 00:05 Message: Logged In: YES user_id=518766 Updating the title to reflect how this will be implemented. ---------------------------------------------------------------------- Comment By: Derek (derekc) Date: 2006-04-17 01:29 Message: Logged In: YES user_id=518766 The TypeLib version could likely be automatically set, however, all the other resources need to be explicitly authored. The problem with automatically grabbing the typelib resources is that it may lead to scenarios in which additional registry keys are added to a setup post-RTM in a patch without the setup developer's knowledge because they didn't explicitly add the new keys. This in turn may lead to component violations and a broken setup. What we can and should do for this situation is recognize type libraries in Heat and automatically pull out their registration that way. This is how we currently advise people to deal with DLL SelfReg. ---------------------------------------------------------------------- Comment By: anfortas (anfortas) Date: 2005-02-12 17:12 Message: Logged In: YES user_id=1203922 I've posted a utility, with source code, to extract this information into an include file: http://gauss.dynalias.net/blog/archive/2005/02/07/wixtlib.asp x ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=642717&aid=1115450&group_id=105970 ------------------------------------------------------------------------- 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-devs mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wix-devs
