I'm bumping this thread since I really need help with this problem.
In a nutshell, the question is this:
*During an upgrade, what can cause that one of the /unchanged/ msi's won't
get the new bundle id registered as a dependency in the registry, which
makes Burn wanting to uninstall it?*
This is
Preprocessor variables are case-sensitive. Does using $(var.PLATFORM) fix it
?
-Original Message-
From: StevenOgilvie [mailto:sogil...@msn.com]
Sent: 13 September 2012 00:05
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] define element for ProgramFilesFolder not working in
inclu
Hi,
I'm creating web application, under Deafult Web Site,adding binding to
ssl.Using wix 3.6
This is my
code:ComponentId="InstallCertificate"Guid=""KeyPath="yes">iis:CertificateId="Company"Name="Company"StoreName="my"StoreLocation="localMachine"CertificatePath="[CERT_FILE_PATH]"PFXPassword="[CERT
Hi All, trust everyone is well.
I've generated a patch file (.msp) and I would like to extract the content
of this file just like dark.exe does for .msi
the reason i'm trying to do this is because i would like to see before hand
what files will be updated.
also one more question is there a way t
Hello,
My WiX MSI package allows same version upgrades with: .
However when using this with my Manager Bootstrapper Application I never
get the RelatedOperation of a MinorUpgrade or MajorUpgrade in the
DetectRelatedBundle event. I only get RelatedOption.None. The process
indeed upgrades the previ
When I want to see what is in a patch, I load the MSI into Insted (this works
with Orca too, If I remember rightly), then select "view patch" from the
menu. The differences applied by the patch are highlighted in colour.
-Original Message-
From: Muzikayise Flynn Buthelezi [mailto:muzkay...
There is a nicer tool called instedit shows the relationship of each element...
__
Steven Ogilvie
3 - 45 Bertrand Street
Ottawa, ON
Canada
K1M 1Y5
Mobile: +1 613 299-2121
E-mail: sogil...@msn.com
-Original Message-
From: Peter Shirtcliffe
Date: Thu, 13 Sep 2012 12:1
Hi Peter,
thanks for kindly getting back to me.
yeah i know about Orca but cant call orca via command line.
basically what i'm trying to do is the following:
- extract the contents of the .msp file and export this list into a file,
therefore we will have a record of what will be updated without
Hi Steven,
thanks for kindly getting back to me, i will checkout this tool.
thanks again,
On Thu, Sep 13, 2012 at 2:18 PM, Steve Ogilvie wrote:
> There is a nicer tool called instedit shows the relationship of each
> element...
> __
> Steven Ogilvie
>
> 3 - 45 Bertrand Str
>Some comments below; they may not fix your problem, but point to other
>issues in the WXS:
Thanx for all your hints!
>
>> -Original Message-
>> From: Branko Horvat [mailto:branko_horvat@...]
>> Sent: Wednesday, September 12, 2012 09:27
>> To: wix-users@...
>> Subject: [WiX-users] wix
Enybody help me.
1. I tried to instal my service with implemented Installer class through
command prompt with installutil.exe pointed to the Release folder of my
service project - all installs and starts well.
2. I tried to add Visual Studio Installer project to my service project -
all installs
Hi Alex
In the custom action look at Impersonate="no"
Read the info on it :)
Steve
-Original Message-
From: alex376 [mailto:asd734jcv9d...@yandex.ru]
Sent: September-13-12 9:06 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] How to solve problem with failed to start ser
> -Original Message-
> From: Branko Horvat [mailto:branko_hor...@hotmail.com]
> Sent: Thursday, September 13, 2012 12:57
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] wix ftdi drivers
>
>
> >> C:\Users\hob\Documents\WiX\ftdiinstall.wsx(29)
> >> C:\Users\hob\Documents\Wi
Are you DOMZE on StackOverFlow?
From: "alex376"
Sent: Thursday, September 13, 2012 8:09 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] How to solve problem with failed to start service
because of unsufficient privileges?
Enybody help me
Okay this is wierd...
if I remove the custom action from the Merge Module and place it in my
product.wxs the path is "created" properly by using
This gets properly changed: [ProgramFilesFolder] BUT the same line as above
in my merge module does NOT...
Line from log file:
PROPERTY CHANGE: Adding
I've used MSIX in the past to break open MSP's.
-Original Message-
From: Muzikayise Flynn Buthelezi [mailto:muzkay...@gmail.com]
Sent: 13 September 2012 13:34
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Extract contents of .MSP file just like dark d
If includes:
Then I would expect the following to work:
Notice that I have $(var.PlatformProgramFilesFolder) enclosed in []. If you
look at the custom action in the merge module using a table editor (orca and
instedit come to mind) then it should look like this:
Hey Edwin,
did as you said and no go...
got this in the merge module:
SetEALNBService.CA23A0DC_B2DE_4F2C_9E74_FD373F99E9D751
EALNBService.CA23A0DC_B2DE_4F2C_9E74_FD373F99E9D7
"""[ProgramFilesFolder.CA23A0DC_B2DE_4F2C_9E74_FD373F99E9D7]\MyCompany\MyProduct\Services\EnterpriseAuditLogService\NSe
Oh, I see that the properties are getting modularized:
SetEALNBService.CA23A0DC_B2DE_4F2C_9E74_FD373F99E9D7
EALNBService.CA23A0DC_B2DE_4F2C_9E74_FD373F99E9D7
ProgramFilesFolder.CA23A0DC_B2DE_4F2C_9E74_FD373F99E9D7
There is a way to avoid that but I'm not familiar with the technique as I don't
us
I appreciate the help!
Steve
-Original Message-
From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com]
Sent: September-13-12 12:52 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] define element for ProgramFilesFolder not working in
incl
thanks for the info, but SuppressModularization="yes" didn't work either :(
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/define-element-for-ProgramFilesFolder-not-working-in-include-file-tp7580463p7580488.html
Sent from the wix-users mailing lis
I *think* you want to use the following in the same fragment where you define
your CustomActions:
The documentation says: Use to suppress modularization of this property
identifier in merge modules. Using this functionality is strongly discouraged;
it should only be necessary as a workaround
try
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/define-element-for-ProgramFilesFolder-not-working-in-include-file-tp7580463p7580487.html
Sent from the wix-users mailing list archive at Nabble.com.
--
AHA!! worked like a charm!! thank you Edwin!!
You da man :)
Steve
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/define-element-for-ProgramFilesFolder-not-working-in-include-file-tp7580463p7580490.html
Sent from the wix-users mailing list archiv
I think just do an admin install, make a copy of it, patch it and then
kdiff the two directories to see which files changed.
From: "Steve Ogilvie"
Sent: Thursday, September 13, 2012 7:22 AM
To: "Peter Shirtcliffe" ,
"wix-users@lists.sourceforge.net"
S
Hello all,
I have following snippet in Bundle.wxs
When I build and run my exe, it does NOT give the UI and installation
doesn't work.
ht.xml
http://wixtoolset.org/schemas/thmutil/2010";>
#(loc.Captio
Hello all,
I want to know if there are any guidelines (best practices) to care about
before clubbing 2 MSI s together using burn. For e.g. I have m1 and m2 as
two msi s.
Both the msi have their own LaunchConditions (which may overlap) where they
check before install (like .NET framework version,
Not in the WiX toolset today, no. You basically want a BA that supports
this declaratively. The wixstdba doesn't.
On Wed, Sep 12, 2012 at 1:59 PM, wrote:
> Hi all - really glad to see 3.6 is out ! We have an MSI with
> upgrade-related logic implemented by the MajorUpgrade element:
> Specificall
The RelatedOption.None is how you know. In WiX v3.7 you also get the
relation type which will further inform you that you have a related Bundle
that is an upgrade but it's operation is None (i.e not upgrade and not
downgrade).
On Thu, Sep 13, 2012 at 4:54 AM, Gregory Beaty wrote:
> Hello,
>
> My
Do you want a single unified installation experience for the two MSIs? If
no, then you don't want Burn.
On Thu, Sep 13, 2012 at 3:28 PM, vchauras wrote:
> Hello all,
>
> I want to know if there are any guidelines (best practices) to care about
> before clubbing 2 MSI s together using burn. For
Have you considered .wixlibs instead? They don't have any of these issues.
On Thu, Sep 13, 2012 at 11:24 AM, StevenOgilvie wrote:
> AHA!! worked like a charm!! thank you Edwin!!
>
> You da man :)
>
> Steve
>
>
>
> --
> View this message in context:
> http://windows-installer-xml-wix-toolset.6875
Source repository is Mercurial on CodePlex. Pick the branch you want the
code for. The default branch has no code (today).
On Wed, Sep 12, 2012 at 12:07 PM, Dennis Oleksyuk wrote:
> Thank you. I have missed the obvious. I was looking all over the places for
> a source repository.
> ---
> Kind re
I think I heard someone mention it before but I do not believe there is a
bug tracking the behavior.
On Wed, Sep 12, 2012 at 8:30 AM, StevenOgilvie wrote:
> Hi,
>
> I am using WIX 3.6 (release) and VS2010...
>
> I am using burn to chain a bunch of MSI's, one of which is my main install
> (the ot
What is the diff between a lib and merge modules
__
Steven Ogilvie
3 - 45 Bertrand Street
Ottawa, ON
Canada
K1M 1Y5
Mobile: +1 613 299-2121
E-mail: sogil...@msn.com
-Original Message-
From: "Rob Mensching-7 [via Windows Installer XML (WiX) toolset]"
Date: Fri, 14 S
You can only suppress elevation if your make all of your MSIs and content
per-user installs. Otherwise, you need the UAC prompt or the installs will
not succed.
On Wed, Sep 12, 2012 at 9:21 AM, Erkan wrote:
> Thanks for clarifying. We were able to suppress UAC by using
> ApplicationRequiresElevat
Thanks.It'd be best if all this was captured in a bug to be investigated
On Wed, Sep 12, 2012 at 4:43 PM, Tim Comport wrote:
> Here are the logs from the exact same test but with the SceduleReboot
> element
> commented out of Package A. This upgrade is successful.
>
> The main difference I see i
There are a number of mysterious things in this log that need more
information to debug. For example:
[170C:1710][2012-09-10T13:43:58]: Detected related
package:{02BA91DA-3C08-45ED-854E-343B5BBDCE40}, scope: PerMachine, version:
2.1.0.0, language: 0 operation: MajorUpgrade
[170C:1710][2012-09-10T1
http://www.robmensching.com/blog/posts/2008/10/10/What-are-.wixlibs-and-why-would-you-use-them
On Thu, Sep 13, 2012 at 7:29 PM, StevenOgilvie wrote:
> What is the diff between a lib and merge modules
> __
> Steven Ogilvie
>
> 3 - 45 Bertrand Street
> Ottawa, ON
> Canada
> K1M
The log file should provide a bit more detail. I expect the problem is that
you're missing all the required pages for wixstdba. Take a look at the
src\ext\BalExtension\wixstdba\Resources\RtfTheme.xml file for an example of
all the pages and controls needed.
On Thu, Sep 13, 2012 at 12:33 PM, vchaur
Thanks Rob.
I do have another issue. How do I disable the ability for the BA to install
multiple versions of my application? It seems that during an upgrade it
installs an entirely new app and there ends up being multiple entries in
Add/Remove programs.
Are there any examples of a managed BA for
Thanks Rob.
I do have another issue. How do I disable the ability for the BA to install
multiple versions of my application? It seems that during an upgrade it
installs an entirely new app and there ends up being multiple entries in
Add/Remove programs.
Are there any examples of a managed BA for
Sorry for the double post.
Greg Beaty
greg.bea...@gmail.com
On Fri, Sep 14, 2012 at 12:19 AM, Gregory Beaty wrote:
> Thanks Rob.
>
> I do have another issue. How do I disable the ability for the BA to
> install multiple versions of my application? It seems that during an
> upgrade it installs a
Hi All,
My first installer uses burn to install prerequisites (.NET 4.0 and visual
c++ redist).
On a machine with .NET already installed, everything seems fine.
On my XP box, Burn installs .NET OK, then prompts for a file, why?, how do I
stop this?
LOG ---
1. Bundles with the same UpgradeCode have an upgrade relationship.The
higher version removes the lower version. Same versions but built at
different times can end up in the situation you describe.
2. There should be very few differences between gettinga BA written for
NETFX 3.5 vs. 4.0. Actually
/[170C:1710][2012-09-10T13:43:58]: Detected related
package:{02BA91DA-3C08-45ED-854E-343B5BBDCE40}, scope: PerMachine, version:
2.1.0.0, language: 0 operation: MajorUpgrade
[170C:1710][2012-09-10T13:43:58]: Detected related
package:{02BA91DA-3C08-45ED-854E-343B5BBDCE40}, scope: PerMachine, version:
45 matches
Mail list logo
