Re: [WiX-users] Problem in Getting the path of executable file and scripts in WIX Installer

It's not exactly clear what you're doing, but the way this works (to state the obvious maybe) is that you build the MSI file on your dev machine and then take that MSI file to other machines and run it to install the product. If you have a problem installing the MSI file on another machine, then

[WiX-users] System.AppDomain.Load error on EmbeddedUI Assembly

Using WiX 3.8 RTM. I've tasked with writing an EmbeddedUI (I know, a custom Burn bootstrapper would be much better, but that approach was rejected). So, I've gotten things to the point of loading, and I get this in the log: MSI (c) (54:70) [09:52:10:736]: EEUI - Running MsiEmbeddedUI code MSI

[WiX-users] Burn setting InstallFolder depending 32/64 bit

Hello! I want to set the InstallFolder variable depending if the actual System is 32 or 64 bit. I have a Bootstrapper which installs several MSI and Exe Files depending if they are 32 or 64 bit (For this I use the attribute Installcondition=NOT VersionNT64). I use the HyperlinkLicense -UI

Re: [WiX-users] System.AppDomain.Load error on EmbeddedUI Assembly

Gasp. Sometimes I am the king of typos. s/Microsoft.Enterprise.Deployment/Microsoft.Deployment.WindowsInstaller/g -Original Message- From: John Cooper Sent: Monday, May 12, 2014 10:07 AM To: General discussion for Windows Installer XML toolset. (wix-users@lists.sourceforge.net)

Re: [WiX-users] System.AppDomain.Load error on EmbeddedUI Assembly

The config file must be named CustomAction.config. On Mon, May 12, 2014 at 10:06 AM, John Cooper jocoo...@jackhenry.comwrote: Using WiX 3.8 RTM. I've tasked with writing an EmbeddedUI (I know, a custom Burn bootstrapper would be much better, but that approach was rejected). So, I've

Re: [WiX-users] Burn setting InstallFolder depending 32/64 bit

Consider using ProgramFiles6432Folder to initialize the burn variable. http://wixtoolset.org/documentation/manual/v3/bundle/bundle_built_in_variables.html When the chain needs to install both 32 bit apps and 64 bit drivers on a 64 bit system then I define two burn variables InstallFolder and

Re: [WiX-users] System.AppDomain.Load error on EmbeddedUI Assembly

But that gives me an idea. I'll just put a stub custom action with a [Custom Action] attribute and see what happens. -- John Merryweather Cooper Build Install Engineer - ESA Jack Henry Associates, Inc.® Shawnee Mission, KS  66227 Office:  913-341-3434 x791011 jocoo...@jackhenry.com

Re: [WiX-users] System.AppDomain.Load error on EmbeddedUI Assembly

Yes, I started there. Exactly the same error. I've been permuting from CustomAction.config since then. -- John Merryweather Cooper Build Install Engineer - ESA Jack Henry Associates, Inc.® Shawnee Mission, KS  66227 Office:  913-341-3434 x791011 jocoo...@jackhenry.com www.jackhenry.com

Re: [WiX-users] System.AppDomain.Load error on EmbeddedUI Assembly

Well, that wasn't fun. Looks like UI and CustomAction entry points are mutually exclusive. So, the Pack target throws a System.NonSupported.Exception. -- John Merryweather Cooper Build Install Engineer - ESA Jack Henry Associates, Inc.® Shawnee Mission, KS  66227 Office:  913-341-3434

[WiX-users] Bootstrapper-UI: Text from Startpage overlapping with text from Modifypage

Hello! When I install my setup, it shows the InstallHeader and InstallMessage on the first page (startpage) and not on the other pages, like it should do. But when I installed my setup and start my setup again, the modifypage appears with the ModifyHeader AND the InstallHeader and

Re: [WiX-users] System.AppDomain.Load error on EmbeddedUI Assembly

Ah! Ran MakeSfxCA.exe from the command line and it appears the magic name is EmbeddedUI.config. -- John Merryweather Cooper Build Install Engineer - ESA Jack Henry Associates, Inc.® Shawnee Mission, KS  66227 Office:  913-341-3434 x791011 jocoo...@jackhenry.com www.jackhenry.com

Re: [WiX-users] Burn setting InstallFolder depending 32/64 bit

The default install directory for an install is usually set internally by the MSI, setting the default folder with a set property custom action. Your question implies that you don't know what your MSI would do if it was deployed outside of Burn. If the MSI's path locations aren't properly managed

Re: [WiX-users] System.AppDomain.Load error on EmbeddedUI Assembly

Naming the config file to EmbeddedUI.config was all it took. -- John Merryweather Cooper Build Install Engineer - ESA Jack Henry Associates, Inc.® Shawnee Mission, KS  66227 Office:  913-341-3434 x791011 jocoo...@jackhenry.com www.jackhenry.com -Original Message- From: John Cooper

[WiX-users] What does '' and '!' inside CDATA[] do?

Does anyone know the meaning of '!' and '' in front of AAA below? Custom Action='_xxx' After='_yyy' ![CDATA[!AAA=3 And PATCH And BBB=0]] /Custom Custom Action='_zzz' After='_xxx' ![CDATA[AAA=3 And CCC1 And DDD=1]] /Custom Thanks, George

Re: [WiX-users] What does '' and '!' inside CDATA[] do?

Scroll down here for explanations about the stated of various features and components: http://msdn.microsoft.com/en-us/library/aa368012(v=vs.85).aspx --- Phil Wilson On Mon, May 12, 2014 at 10:14 AM, George Fleming gef...@microsoft.com wrote: Does anyone know the meaning of '!' and

Re: [WiX-users] What does '' and '!' inside CDATA[] do?

That depends. They look like Component or Feature ID's. In which case, install states are being evaluated. The link Phil points to is definitive. -- John Merryweather Cooper Build Install Engineer - ESA Jack Henry Associates, Inc.® Shawnee Mission, KS  66227 Office:  913-341-3434 x791011

Re: [WiX-users] What does '' and '!' inside CDATA[] do?

Terrible Naming Convention there... :) ! = the Not Operator and = Concatenation Operator: For Custom Action 1 to Complete: AAA cannot = 3 and the patch level must be 0 For Custom Action 2 to Complete: AAA must = 3 and 3 is appended to the value of AAA after the completion of _xxx, CCC

Re: [WiX-users] What does '' and '!' inside CDATA[] do?

Scratch this... other than the terrible naming... Proper Answer: For Custom Action 1 to Complete: The install State of Feature AAA must be 3 and the Patch Level stored in BBB must be 0 For Custom Action 2 to Complete: The Action State of Feature AAA must be 3, while CCC cannot = 1 and DDD