Hi Guys, The article on the contents of an MSI at this link is excellent: http://appdeveloper.intel.com/en-us/article/troubleshooting-validation-failures Highly recommended for anyone submitting any type of MSI installer! I was having problems getting an MSI built with War Setup to validate (comes back with app cannot launch from AppUp client - error -13). I can probably hack the MSI about with ORCA to get it through (eventually), but in the meantime I have found a contradiction: The above article insists that the field Shortcut > Target should NOT contain square brackets. War Setup however produces square brackets here, so I looked at the MSDN link provided by the article to explain why (http://msdn.microsoft.com/en-us/library/aa369212(VS.85).aspx). Fair enough, identifiers cannot have square brackets. All good. But then I read this related MSDN page: http://msdn.microsoft.com/en-us/library/aa371847(VS.85).aspx As you can see, it refers to the Target field as a SHORTCUT, but an IDENTIFIER. If you follow the extra help information on a SHORTCUT type, it DOES allow square brackets: http://msdn.microsoft.com/en-us/library/aa371844(v=VS.85).aspx So my question. Is there a special reason why the AppUp client does not like square brackets in the Target field when it is a completely acceptable thing to do according to MSDN. I have provided an extract of the text below: "The Shortcut data type is usually used in the Target column of the Shortcut table. If it contains square brackets ([ ]), the shortcut target is evaluated as a Formatted string. Otherwise, the shortcut is evaluated as an Identifier and must be a valid foreign key into the Feature table." I am not saying this issue will fail validation and I noticed when I used ORCA I had TWO shortcuts, so I have something to hack and re-submit, but the article did seem to provide conflicting information with MSDN, and I am very curious to the why. Thanks!
For more complete information about compiler optimizations, see our Optimization Notice.