|
From: SourceForge.net <no...@so...> - 2006-07-22 03:49:41
|
Bugs item #1526833, was opened at 2006-07-21 23:49 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=642714&aid=1526833&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: light Group: None Status: Open Resolution: None Priority: 5 Submitted By: Rob (rmacfadyen) Assigned to: Nobody/Anonymous (nobody) Summary: Deleting the .MSI if the ICE checks fail... not good? Initial Comment: If an ICE produces an error the .MSI seems to be deleted. This can lead to error messages that there is no straight-forward way to diagnose. For example, given the following custom action: <CustomAction Id="Set_ARPREADME" Property="ARPREADME" Value="[TARGETDIR]\ReadMe.Txt" Execute="deferred" /> This compiles fine, links fine, but generates the following ICE error: .\Product.wxs(142) : error LGHT0204 : ICE68: Invalid custom action type for action 'Set_ARPREADME'. Because the error message does not display the custom action type it is a bit difficult to determine what exactly is wrong. I'm sure it would be a lot of work... but shouldn't all the ICE checks be incorporated into Candle/Light directly? Regards, Rob ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=642714&aid=1526833&group_id=105970 |