|
Never realised MSI itself was such a dark art, and top of it the bloody WiX, only delved into last week. Simple question that if answered would make all my dreams come true (well make me be able to finish the bloody nearly finished setup regime for software product) I have a c# custom action to select an option and enter some text, how can I reference and act on variables in it in the wxs. Really id like to optionally install different components depending on the select but I cant seem to reference the property returned in session. Here is the property and the DLL binding sample from the wxs code:code:code:code:
|
#
¿
Sep 12, 2017 19:43
|
|
|
|
| # ¿ Apr 20, 2024 03:33 |
|
|
If anyone is interested I found the solution from some really nice people on the WiX user mailing list which is at <wix-users@lists.wixtoolset.org> Its to do with the sequence of events. Basically there is an UI sequence and a EXE sequence, both of which may be occurring depending on what you are trying to do. Its documented somewhere but its where to use my event that was my problem. Changed my custom dll to run before CostInitialize and the properties go back to the wxs because its after that point they get evaluated in the wxs. I like this thing but bloody hell is it badly documented by the provider/s, basically all the documentation comes from the community. Have to use it, want to use it, but cant figure out how it works in short order if that makes sense. Call me old school if you like but I dont think trying to do something simple rapidly should be some baptism of fire into magic ancient powers. To be fair ultimately MS not wrapping the MSI stuff in way that makes it easy is to blame I think so im not blaming WiX (And the mailing list people are lovely)e: id encourage anyone to join that mailing list if you have any problems/questions, the online documentation is loving shocking for a newbie but those guys are great! Seaside Loafer fucked around with this message at 21:06 on Sep 14, 2017 |
|
#
¿
Sep 14, 2017 13:30
|
|