You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you run "heat payload" on an MSU file it generates a payload with empty Version, Description and ProductName attributes (as they aren't defined for MSU files) and this is an invalid RemotePayload as defined by the schema.
Are these values actually mandatory for an MsuPackage RemotePayload?
The install seems to be happy with Description and ProductName set to any value and Version set to 0.0.0.0.
(Hoping to submit a patch soon that sets Description and ProductName to the MSU name and version to 0.0.0.0 for MSU files.)
Originally opened by neilsl
The text was updated successfully, but these errors were encountered:
If you run "heat payload" on an MSU file it generates a payload with empty Version, Description and ProductName attributes (as they aren't defined for MSU files) and this is an invalid RemotePayload as defined by the schema.
Are these values actually mandatory for an MsuPackage RemotePayload?
The install seems to be happy with Description and ProductName set to any value and Version set to 0.0.0.0.
(Hoping to submit a patch soon that sets Description and ProductName to the MSU name and version to 0.0.0.0 for MSU files.)
The text was updated successfully, but these errors were encountered: