@@ -16,12 +16,25 @@
|
||||
<OutputType>Package</OutputType>
|
||||
|
||||
<!--
|
||||
MSI validation still assumes an installation for the whole machine.
|
||||
Installing into the user's own profile trips three of its rules: a
|
||||
component whose key path is a file (ICE38), a folder it wants listed
|
||||
for removal (ICE64), and a warning that the files will not follow other
|
||||
users of the machine (ICE91). All three describe exactly what was
|
||||
intended here, so they are turned off rather than worked around.
|
||||
The ICE checks run inside the Windows Installer service, and a build
|
||||
agent has no access to it: every single check comes back as WIX0217,
|
||||
"The Windows Installer Service could not be accessed", and the build
|
||||
fails on close to a hundred of them. Since the release is built by the
|
||||
agent, validation cannot be part of it.
|
||||
|
||||
It stays switchable rather than deleted: -p:SuppressValidation=false
|
||||
turns it back on where the service does answer, which is any ordinary
|
||||
desktop machine.
|
||||
-->
|
||||
<SuppressValidation Condition="'$(SuppressValidation)' == ''">true</SuppressValidation>
|
||||
|
||||
<!--
|
||||
What validation says when it does run. MSI still assumes an
|
||||
installation for the whole machine, and installing into the user's own
|
||||
profile trips three of its rules: a component whose key path is a file
|
||||
(ICE38), a folder it wants listed for removal (ICE64), and a warning
|
||||
that the files will not follow other users of the machine (ICE91). All
|
||||
three describe exactly what was intended here.
|
||||
-->
|
||||
<SuppressIces>ICE38;ICE64;ICE91</SuppressIces>
|
||||
|
||||
|
||||
Reference in New Issue
Block a user