Closed wixbot closed 8 years ago
Release
changed fromv3.10
tov3.x
Originally changed by
rseanhall
AssignedTo
set toshall
The config file must be EmbeddedUI.config, not CustomAction.config.
Originally posted by
rseanhall
AssignedTo
changed fromshall
to`
Resolutionset to
notabugStatus
changed from
Opento
Resolved`
Great. Thank you. The change to the EmbeddedUI.config helps.
It is highly unexpected/unusual that the command line interface expects the argument (which is a file path) with the 'hard codded' file name. But it wouldn't be a huge problem if some sort of error/warning is produced by MakeSfxCA.exe.
Interestingly enough it does the validation and reports the problem if the specified assembly contains both EmbeddedUI and CA implementations. It would be only logical if the same validation routine reports that the specified config file will has unexpected name be ignored. Or better yet if it returns the error.
Is it possible that you can consider extending the input validation? Please let me know if a new feature request needs to be logged.
Thank you for your help.
Originally posted by
taras
Yes, please open a feature request.
Great. Done: http://wixtoolset.org/issues/4900/ Thank you
Originally posted by
taras
With WiX v3.10.0.2103 (and earlier) the EmbeddedUI is always hosted by CLR v2.0 even if CLR v4.0 is present on the target system and the embedded app.config properly maps the CLR versions.
Note the test-case I have prepared (TestCase.7z) demonstrates how two assemblies (EmbeddedUI and CustomAction) built and packed the same way are hosted by different CLRs within the same setup at runtime.
The instructions on how to run the test-case are in the readme.txt (form the TestCase.7z package).