See... what is wrong here? I included a "reference" to the
backupSettingsAction project in the WiX project.
--
View this message in context:
http://windows-installer-
"The path of the CommonAppData directory is found in the "CommonAppData"
property after CostFinalize. The same with all the entries in the Directory
table."
Okay, those are properties in the WiX file, no? How can I pass that to my
C# program (custom action) to manipulate the file? I'm confuse
I am now working on getting the custom action going to back up the existing
settings.xml file. I am using this page as a guide:
http://blogs.msdn.com/b/jasongin/archive/2008/05/23/custom-action-project-templates.aspx
I have created a custom action project, and it builds. I am a bit confused
th
AH... okay, your response now finally makes some sense. Custom action is
what I was just looking at, as I don't have much of a notion of the
patching...
Just for the record, I DID NOT author the original installer for this
application, I am simply coming in after the fact with a new version.
I have already tried this! I have been through several rounds of it, and the
problem is that if RemoveExistingProducts is set after InstallFinalize
(which makes the Settings.xml file remain intact), the CompanionFile does
work to show that the file is replaced, however, the Pathways.MDF file then
Okay! I have finally more closely identified the problem I'm having. In my
installer, I was attempting to get a settings file to REMAIN INTACT on a
major upgrade. I finally got this to work with the suggestion to set
This is successful in forcing this component to leave the origina
Hello! So I have this WiX problem doing a major upgrade. I have made some
progress since I started, but I'm fairly stumped on exactly what to do now.
I was having trouble with the SettingsXml file, but now it does remain
intact as I need it to. Then I tried to make the two database components
Hello!
So I am working on a new version of a program already out in the field.
Thanks to a finger pointing in the right direction I have gotten the new
installer to run when clicked on (before, the old one ran), now I have
my upgrade stuff working fine and dandy, though I have just one problem.
Hello!
When I run my new Setup.msi file on a system that already has a previous
version of the program installed, instead of actually running my new
Setup.msi file, the OLD setup file is run, and I am given the options of
uninstall or repair or cancel. I would like to be able to install a new
9 matches
Mail list logo
