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 (c) (54:9C) [09:52:10:746]: Cloaking enabled.
MSI (c) (54:9C) [09:52:10:746]: Attempting to enable all disabled privileges
before calling Install on Server
MSI (c) (54:9C) [09:52:10:746]: Connected to service for CA interface.
SFXCA: Extracting embedded UI to temporary directory:
C:\Users\JoCooper\AppData\Local\Temp\2\MSI8616
SFXCA: Binding to CLR version v2.0.50727
Error: could not load embedded UI class
JackHenry.Enterprise.Deployment.ResponseFileDialog.ResponseFileEmbeddedUI from
assembly: JackHenry.Enterprise.Deployment.ResponseFileDialog
System.BadImageFormatException: Could not load file or assembly
'JackHenry.Enterprise.Deployment.ResponseFileDialog' or one of its
dependencies. This assembly is built by a runtime newer than the currently
loaded runtime and cannot be loaded.
File name: 'JackHenry.Enterprise.Deployment.ResponseFileDialog'
at System.Reflection.Assembly._nLoad(AssemblyName fileName, String codeBase,
Evidence assemblySecurity, Assembly locationHint, StackCrawlMark& stackMark,
Boolean throwOnFileNotFound, Boolean forIntrospection)
at System.Reflection.Assembly.nLoad(AssemblyName fileName, String codeBase,
Evidence assemblySecurity, Assembly locationHint, StackCrawlMark& stackMark,
Boolean throwOnFileNotFound, Boolean forIntrospection)
at System.Reflection.Assembly.InternalLoad(AssemblyName assemblyRef,
Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection)
at System.Reflection.Assembly.InternalLoad(String assemblyString, Evidence
assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection)
at System.AppDomain.Load(String assemblyString)
at
Microsoft.Deployment.WindowsInstaller.EmbeddedUIProxy.InstantiateUI(Session
session, String uiClass)
Assembly manager loaded from:
C:\Windows\Microsoft.NET\Framework\v2.0.50727\mscorwks.dll
Running under executable C:\Windows\SysWOW64\MsiExec.exe
--- A detailed error log follows.
=== Pre-bind state information ===
LOG: User = JXCHANGECORP\JoCooper
LOG: DisplayName = JackHenry.Enterprise.Deployment.ResponseFileDialog
(Partial)
LOG: Appbase = file:///C:/Users/JoCooper/AppData/Local/Temp/2/MSI8616
LOG: Initial PrivatePath = NULL
Calling assembly : Microsoft.Deployment.WindowsInstaller, Version=3.0.0.0,
Culture=neutral, PublicKeyToken=ce35f76fcda82bad.
===
LOG: This bind starts in default load context.
LOG: No application configuration file found.
LOG: Using machine configuration file from
C:\Windows\Microsoft.NET\Framework\v2.0.50727\config\machine.config.
LOG: Policy not being applied to reference at this time (private, custom,
partial, or location-based assembly bind).
LOG: Attempting download of new URL
file:///C:/Users/JoCooper/AppData/Local/Temp/2/MSI8616/JackHenry.Enterprise.Deployment.ResponseFileDialog.DLL.
ERR: Failed to complete setup of assembly (hr = 0x8013101b). Probing terminated.
MSI (c) (54:70) [09:52:10:995]: EEUI - Install Failure: InitializeEmbeddedUI on
a UI DLL returned: 1603
Info 1603.Fatal error during installation.
So, it appears that the DTF
assembly-Microsoft.Deployment.WindowsInstaller.dll-is forcing the load context
to CLR 2.0. I know .NET custom action wrapper has to handle this somehow. I
have tried numerous Config file names, but the one I haven't tried is
Microsoft.Enterprise.Deployment.config. Is this what I need to avoid being
trapped in CLR 2.0-or something else? The EmbeddedUI is being packaged:
PackCustomAction:
"C:\Program Files (x86)\WiX Toolset v3.8\bin\..\sdk\MakeSfxCA.exe" "D:\tfs\ES
A\Installer\Dev\ResponseFileDialog\obj\Debug\JackHenry.Enterprise.Deployment.
ResponseFileDialog.CA.dll" "C:\Program Files (x86)\WiX Toolset v3.8\bin\..\sd
k\x86\SfxCA.dll" "D:\tfs\ESA\Installer\Dev\ResponseFileDialog\obj\Debug\JackH
enry.Enterprise.Deployment.ResponseFileDialog.dll" "C:\Program Files (x86)\Wi
X Toolset v3.8\bin\Microsoft.Deployment.WindowsInstaller.dll;C:\Program Files
(x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5\Presentati
onCore.dll;C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.N
ETFramework\v4.5\PresentationFramework.dll;C:\Program Files (x86)\Reference A
ssemblies\Microsoft\Framework\.NETFramework\v4.5\WindowsBase.dll;D:\tfs\ESA\I
nstaller\Dev\ResponseFileDialog\JackHenry.Enterprise.Deployment.ResponseFileD
ialog.config"
Searching for custom action entry points in JackHenry.Enterprise.Deployment.R
esponseFileDialog.dll
Loaded dependent assembly: C:\Program Files (x86)\WiX Toolset v3.8\bin\Mi
crosoft.Deployment.WindowsInstaller.dll
Searching for an embedded UI class in JackHenry.Enterprise.Deployment.Respons
eFileDialog.dll
Modifying SfxCA.dll stub
Copying file version info from D:\tfs\ESA\Installer\Dev\ResponseFileDialog\ob
j\Debug\JackHenry.Enterprise.Deployment.ResponseFileDialog.dll to D:\tfs\ESA\
Installer\Dev\ResponseFileDialog\obj\Debug\JackHenry.Enterprise.Deployment.Re
sponseFileDialog.CA.dll
Packaging files
JackHenry.Enterprise.Deployment.ResponseFileDialog.dll
Microsoft.Deployment.WindowsInstaller.dll
PresentationCore.dll
PresentationFramework.dll
WindowsBase.dl
JackHenry.Enterprise.Deployment.ResponseFileDialog.config
MakeSfxCA finished: D:\tfs\ESA\Installer\Dev\ResponseFileDialog\obj\Debug\Jac
kHenry.Enterprise.Deployment.ResponseFileDialog.CA.dll
Pointers and suggestions would be greatly appreciated.
--
John Merryweather Cooper
Build & Install Engineer - ESA
Jack Henry & Associates, Inc.(r)
Shawnee Mission, KS 66227
Office: 913-341-3434 x791011
[email protected]<mailto:[email protected]>
www.jackhenry.com<http://www.jackhenry.com/>
NOTICE: This electronic mail message and any files transmitted with it are
intended
exclusively for the individual or entity to which it is addressed. The message,
together with any attachment, may contain confidential and/or privileged
information.
Any unauthorized review, use, printing, saving, copying, disclosure or
distribution
is strictly prohibited. If you have received this message in error, please
immediately advise the sender by reply email and delete all copies.
------------------------------------------------------------------------------
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos.
Get unparalleled scalability from the best Selenium testing platform available
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net/sfu/SauceLabs
_______________________________________________
WiX-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-users
