Hello Gents,
I have a question about the generated .msi file.
The registry components in the Component table do not have a keypath, is there a reason for that?
This is cuasing ICE validation errors on some strict ICE checks we must pass.
I.E.
Component table row with error
Component..............ComponentId.....................................Directory.....Attributes.....Condition.............KeyPath
ID_5bPWR370_15d......{4A2F5697-1B46-4380-8F98-A9FD3FA1CC84}..SourceDir.....64..............AWR370 = "TRUE"....
Thanks
.MSI Component Table - missing keypath?
-
norbertjurkiewicz
- Posts: 16
- Joined: Thu Aug 02, 2012 11:07 am
-
FrancescoT
- Site Admin
- Posts: 5361
- Joined: Sun Aug 22, 2010 4:28 am
Re: .MSI Component Table - missing keypath?
Dear User
We ran the full msi validation suite available in Orca 3.1 on a setup with a number of registry keys, but we was unable to reproduce this error.
Perhaps if you can clarify exactly which validation suite he tried and which Write Registry statements cause the failure in question.
Regards
We ran the full msi validation suite available in Orca 3.1 on a setup with a number of registry keys, but we was unable to reproduce this error.
Perhaps if you can clarify exactly which validation suite he tried and which Write Registry statements cause the failure in question.
Regards
Francesco Toscano
InstallAware Software
White Papers (HowTos) - http://www.installaware.com/publication ... papers.htm
Publications - http://www.installaware.com/publications-review.htm
InstallAware Help -F1 anywhere in the InstallAware IDE
InstallAware Software
White Papers (HowTos) - http://www.installaware.com/publication ... papers.htm
Publications - http://www.installaware.com/publications-review.htm
InstallAware Help -F1 anywhere in the InstallAware IDE

