-
I realise that there is a similar discussion recently, but this is WixUI. I implemented the changes required from that discussion, being to add the extension via command "wix extension add -g WixToolset.Util.wixext" and then include the extension in the build command as is shown below. I converted my v3 .wxs script to v4 using the conversion tool. Declaration shows (as converted by the conversion tool)... <Wix xmlns="http://wixtoolset.org/schemas/v4/wxs" xmlns:ui="http://wixtoolset.org/schemas/v4/wxs/ui"> Element reference further down (as converted by the conversion tool), now within the Package element, was Product element previously... <ui:WixUI Id="WixUI_Advanced" /> Cut and paste from the command line...
What should I do? |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 3 replies
-
I did cut and paste the declaration, and it is shown if I attempt to edit the question. I don't know why it's not showing above. |
Beta Was this translation helpful? Give feedback.
-
It turns out I covered exactly this topic very recently in the Deployment Dojo. Check out Episode 37 - Using WixExtensions in WiX v4 to go beyond MSI functionality for all the details. |
Beta Was this translation helpful? Give feedback.
-
I found the problem. I should have installed WixToolset.UI.wixext, as I meant to, and not WixToolset.Util.wixext. Working too late and cutting and pasting the wrong line. |
Beta Was this translation helpful? Give feedback.
I found the problem. I should have installed WixToolset.UI.wixext, as I meant to, and not WixToolset.Util.wixext. Working too late and cutting and pasting the wrong line.