Re: [WiX-users] Preserving install directory on upgrade

That sounds like a promising approach. I'll try that one too. Anyone know any downside of getting the old installdir that way? kind regards, Michael -Ursprüngliche Nachricht- Von: Phil Wilson [mailto:phildgwil...@gmail.com] Gesendet: Samstag, 19. April 2014 20:28 An: General discussion

[WiX-users] Preserving install directory on upgrade

Hi, I recently detected a problem within my installer package (No UI). I implemented it with major upgrade capability to easily install new versions. What I have realized now is, that during major upgrade I loose my previousely set install directory: This is my directory structure: ?xml

Re: [WiX-users] Preserving install directory on upgrade

/blog/posts/2010/5/2/the-wix-toolsets-remember-property-pattern/ Neil -Original Message- From: fom Forstner Michael [mailto:f...@keba.com] Sent: 18 April 2014 13:00 To: General discussion about the WiX toolset. Subject: [WiX-users] Preserving install directory on upgrade Hi, I recently

Re: [WiX-users] Modify MSI version

the property in MSI database from configValue=1 to configValue=2 Is there some inconsistency going on if I do that, or is it okay? kind regards, Michael -Ursprüngliche Nachricht- Von: fom Forstner Michael [mailto:f...@keba.com] Gesendet: Mittwoch, 09. April 2014 13:54 An: General discussion

Re: [WiX-users] Modify MSI version

Park, Glasgow G20 0SP Email Disclaimer -Original Message- From: fom Forstner Michael [mailto:f...@keba.com] Sent: 08 April 2014 09:09 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Modify MSI version Hello, I'm trying to understand how MSI does decide if to use the cached

Re: [WiX-users] Modify MSI version

Nachricht- Von: fom Forstner Michael [mailto:f...@keba.com] Gesendet: Mittwoch, 09. April 2014 10:50 An: General discussion about the WiX toolset. Betreff: Re: [WiX-users] Modify MSI version The PackageCode it was. After updating the SummaryInformation stream via code all works as expected

[WiX-users] Modify MSI version

Hello, I'm trying to understand how MSI does decide if to use the cached package or the original package I start from. Therefore I installed one of my packages with version 1.0.0.0 . After that I opened the package with Orca and change the product version property to 2.0.0.0 and gave the

[WiX-users] Resigning MSI package

Hi, I have a question about resigning MSI packages. My scenario: I built a .NET application to handle a whole bunch of MSI packages as a complete product suite (platform). Those MSI packages hold some custom properties that are used for install/update logic and visual appearance of the

Re: [WiX-users] Running an MSI twice

The upgrade path wouldn't concern me to much, because our end customer relationships are all 1-to-1. But you got me thinking with the signature part. Maybe my approach on this was not quite the best. Maybe I should consider just teaching my internal customer's how to make easy setup projects

[WiX-users] Running an MSI twice

Greetings, I have a question regarding the Major upgrade feature of Wix/MSI. I configured my Wix project to be able to do a major upgrade even on the same version. So only downgrades are not possible. Result: I build version 1.0.0.0 and run it. -- Installs the product. I rebuild version

Re: [WiX-users] Running an MSI twice

Hi, thanks for your respones. I think I may have just been using the wrong words to describe my situation. I'm quite new to Wix/MSI. Let me try to explain the problem with an example. I have created the following small project: == Wix

Re: [WiX-users] Running an MSI twice

Unfortunately not. The idea is that I deliver a base version of a product. My internal customers can add some configuration commands on their own. Now, if they want to change the configuration commands they use my program and change the related propery in the MSI. Then they deliver it to the