Hi, I have created a bundle using wix 3.7 to run 2 msi's in chain. This works
for the 64 bit machine. But the same setup throws "Unhandled exception in
Setup.exe. Access violation reading location " on a 32 bit machine. But
running the msi's individually installs the msi's properly without any
err
Hi,
I'm fairly new to WIX but was unable to find a solution online. I'm trying
to save a PathEdit path to the registry. Once I get to the dialog under
question, the path to the Documents folder is displayed properly, but I am
unable to proceed to the next dialog or change the path with the Change
Hi,
I'm fairly new to WIX but was unable to find a solution online. I'm trying
to save a PathEdit path to the registry. Once I get to the dialog under
question, the path to the Documents folder is displayed properly, but I am
unable to proceed to the next dialog or change the path with the Change
Hi,
I'm fairly new to WIX but was unable to find a solution online. I'm trying
to save a PathEdit path to the registry. Once I get to the dialog under
question, the path to the Documents folder is displayed properly, but I am
unable to proceed to the next dialog or change the path with the Change
Brilliant, thanks for all your help Jacob.
Hope you have a good weekend.
It has been a steep learning curve with WiX but I have enjoyed it and am
pleased with the results.
Dave Moss
Tactical Team Lead
OmPrompt
+44 (0)1235 436014 Direct
davidm...@omprompt.com
www.omprompt.com
OmPrompt Limited
The afterInstallInitialize basically means you are uninstalling the old product
then installing the new one. I believe you need to schedule it later
(afterInstallExecute) in order for the upgrade to keep that file.
afterInstallValidate
(Default) Schedules RemoveExistingProducts a
Hi Jacob,
In the log I am seeing the following:-
MSI (s) (38:3C) [12:15:15:104]: Executing op:
FileCopy(SourceName=rpv1rjfo.con|OmpXLStoCSV.exe.config,SourceCabKey=fil12563A655A510D27A819EB8C6F1C0B37,DestName=OmpXLStoCSV.exe.config,Attributes=512,FileSize=2973,PerTick=65536,,VerifyMedia=1,Ch
Are you sure the file is being replaced?
Ref:
http://www.mombu.com/microsoft/platform-sdk-msi/t-file-versioning-rules-would-disable-the-component-322048.html
later on where it says something like:
MSI (s) (34:00) [13:36:09:766]: File: ...\application.exe.config; Won't
Overwrite; Won't patch; E
Jacob,
The changing GUIDs in the heat extraction was indeed the issue, I can't believe
I didn't notice that.
I do have one more question the application.exe.config files that are deployed
are being overwritten each time the installer runs this is because the
application uses them and changes t
Hi,
Are the registry keys filled with properties entered or modified by the user?
If so, are the registry keys set to default in your patch case?
Am 24.05.2013 um 11:32 schrieb Ravishankar
:
> Hi All,
> My main installer creates some registry entries(Database
> ServerName,Database Name etc)
Hi All,
My main installer creates some registry entries(Database
ServerName,Database Name etc)
I have created a patch using the pcp method and when installing the
patch its overwriting the registry entries created by the main installer
Can anyone please help me out.
Thanks and Regards
Ravi
--
Hi Jacob,
I would like to start by saying thanks for your help with this and sorry I
haven't responded sooner, I am guessing I am on UK time and you are on US time.
Yes the msi works correctly outside the bundle and yes I do increment the
BuildNo MSI Property with each build, this is done by Hu
12 matches
Mail list logo
