Product\@Id = ProductCode property
Product\@Version = ProductVersion property
Correct. I believe both of these are documented in the CHM file. If not, please
raise a bug.
From: mri...@realtyim.com
To: wix-users@lists.sourceforge.net
Date: Fri, 20 Sep 2013 17:12:09 +
Subject: Re:
If I were your custom action I would log everything I could to figure it out.
From: kpet...@otaksoft.com
To: wix-users@lists.sourceforge.net
Date: Fri, 20 Sep 2013 19:47:45 -0700
Subject: Re: [WiX-users] Execution order issue
Thanks for asking the question again (why not after
@Rob,
Why can't a new bundle handle this?
Is there a GUID clash or?
(We're seeing this on a dirty Win 8 VM)
Thanks,
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bootstrapper-errors-tp7582859p7589364.html
Sent from the wix-users mailing
All,
I have a number of .msi's that are built using the WiX toolset, and they are
also made available as a single .exe package using WiX Burn.
A number of those individual installations check for the presence of the Window
File Based Write Filter, and if found will prompt for a reboot and then
You might find catest.dll a helpful tool in this situation.
http://blogs.msdn.com/b/astebner/archive/2005/03/07/388739.aspx?Redirected=true
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Execution-order-issue-tp7588998p7589366.html
Sent from the
Handle what?
On Wed, Oct 2, 2013 at 2:41 AM, rowbot james.row...@microfocus.com wrote:
@Rob,
Why can't a new bundle handle this?
Is there a GUID clash or?
(We're seeing this on a dirty Win 8 VM)
Thanks,
--
View this message in context:
This is a question better asked on wix-devs (to cover the debugging
aspects). The assert is telling you that something is incorrectly passing
NULL to a dutil string function. It *may* be okay but it could also
indicate a huge problem. Try attaching your debugger with both native and
managed code
Ideally a DLL custom action would be added. It would be great if that were
contributed back so that everyone could benefit.
One other concern: the blank guid on your Plugin component means that this file
association, including the Open verb registration, would not be removed when
the
This has been discussed in this mail list and in several bugs before. The issue
is that the documented Purely Wix method requires that the builds be done
from different paths because the files to be compared have to have been linked
into their respective MSIs from different locations. Builds
For the file that should never be upgraded, check out the NeverOverwrite
attribute of the Component element.
From: afor...@cmu.edu
To: wix-users@lists.sourceforge.net
Date: Tue, 24 Sep 2013 09:37:50 -0400
Subject: Re: [WiX-users] Need some help with upgrade support in first
A couple other approaches to build versions (that can also set build versions
into the binaries you build) are included in products like these:
MSBuild Extension Pack
http://www.msbuildextensionpack.com/
MSBuild Community Tasks
https://github.com/loresoft/msbuildtasks
From:
Do you have any PatchFamily declared? What resources/components are included?
From: hinrich@kofax.com
To: wix-users@lists.sourceforge.net
Date: Fri, 27 Sep 2013 08:37:30 +
Subject: [WiX-users] added performance counters are not registered in patch
we are using:
2013/10/2 rowbot james.row...@microfocus.com:
@Rob,
Why can't a new bundle handle this?
Is there a GUID clash or?
(We're seeing this on a dirty Win 8 VM)
Thanks,
You are replying to a message from January and posting no context at
all. I hadn't joined the mailing list yet, so I don't
Why can't you use the current CopyFile element in Wix instead of creating your
own custom action? Use a ComponentSearch to find the old file's location for
upgrade purposes.
Date: Fri, 27 Sep 2013 03:15:27 -0700
From: nkshirsa...@gmail.com
To: wix-users@lists.sourceforge.net
Subject: Re:
The .pdbs for Wix 3.6 RTM are in the wix36-pdbs.zip file on this page:
http://wix.codeplex.com/releases/view/93929
Date: Mon, 30 Sep 2013 10:34:24 +0530
From: ravishankar.krishnasw...@idsnext.com
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] System.OutOfMemoryException
Hi
This is described in the CHM, in the online documentation, and in the tutorial.
From: dusan.pla...@avitech-ag.com
To: wix-users@lists.sourceforge.net
Date: Mon, 30 Sep 2013 16:08:30 +0200
Subject: [WiX-users] How to replace action on next button
Hi there,
I am using mondoUI, and I
Thanks, at first it did not seem to work as the calling app did have failures
and they did not cause the install to fail, but then we had another error that
did fail the install.
So we figured that some returns were not a complete failure and therefore the
return did not cause an install
It is possible to use Restart Manager to avoid the reboot (it will stop
explorer.exe and restart it during the upgrade) if no other users are logged in.
From: nicolas.alva...@gmail.com
Date: Mon, 30 Sep 2013 17:57:04 -0300
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] How to
See
http://blogs.msdn.com/b/heaths/archive/2009/12/21/about-shared-components.aspx
From: nicolas.alva...@gmail.com
Date: Tue, 1 Oct 2013 00:51:36 -0300
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Practical use of wixlibs
I can't find any documentation on best-practices when
Is it possible to make a single MSI/Bundle to handle both Major upgrades and
Minor upgrade/updates?
Thanks
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Authoring-a-Major-Minor-upgrade-in-same-package-tp7589392.html
Sent from the wix-users
2013/10/2 victorwhiskey victorhwhis...@yahoo.com:
Is it possible to make a single MSI/Bundle to handle both Major upgrades and
Minor upgrade/updates?
A major upgrade changes the ProductCode, and works by uninstalling the
existing version and installing the new msi. A minor upgrade doesn't
I've never tried but in thinking it over, it's not possible. I have done
MSI's that might install side by side or in place upgrade at runtime. This
was done through manipulating the upgrade process at runtime. However an
MSI that might be major or might be minor would either have to have
Components have two identities, a local one (used within the MSI, including
in conditions and properties) and a global one (used when identifying a
component from a different MSI or even from outside all MSIs). The local one is
an identifier (alphanumeric string) and the global one is a GUID.
Thanks guys. I've only done installers with major upgrades, so I'm not too
sure it that was possible. So what I'm doing now is keeping the ProductCode
as * for each build I can install upgrade on top of the previous one. Is
this a bad practice then?
Thanks
--
View this message in context:
That's extremely enlightening. I thought having two components in
different products with the same GUID but different installation
directories would be a blatant break of component rules and would just
not work. Allowing uninstallation of shared component. Other clients
exist, but installed to a
A standard custom action should be able to deal with that scenario as well.
From: chr...@iswix.com
To: wix-users@lists.sourceforge.net; wix-users@lists.sourceforge.net
Date: Tue, 1 Oct 2013 17:58:42 -0700
Subject: Re: [WiX-users] How to pass an enumeration as a variable? Allowing
Service
2013/10/2 victorwhiskey victorhwhis...@yahoo.com:
Thanks guys. I've only done installers with major upgrades, so I'm not too
sure it that was possible. So what I'm doing now is keeping the ProductCode
as * for each build I can install upgrade on top of the previous one. Is
this a bad practice
A single bundle can correctly install one MSI as a major upgrade and another
MSI as a minor upgrade in the same chain, if that is what you are asking.
Generally minor upgrades are not what most people think that they are (unless
you are talking about patching). Major Upgrade is what will work
Sort of obscure not-detailed-enough half-mentions on MSDN?
For deep technical dives into Windows Installer Heath is my go-to resource.
From: nicolas.alva...@gmail.com
Date: Wed, 2 Oct 2013 15:45:52 -0300
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Practical use of wixlibs
One more point I should make: Windows Installer differentiates between File
resources and other resources (like Registry, etc.). Thus, if the shared
component has registry and file both (such as COM registrations) the uninstall
will remove the files but not touch the registry entries, so COM
Windows Installer was created in the days of physical software
distribution and small hard disks. Physical software distribution
means you can and should put all prerequisites in the disc. It doesn't
matter if you ship a dozen different products and all of them waste
100MB with the exact same
Thanks. I bought a book and am reading through it.
It just struck me as odd that the online example placed a GUID in an id,
instead of defining an attribute named Guid. For example
Product
Name='Foobar 1.0'
Id='YOURGUID-86C7-4D14-AEC0-86416A69ABDE'why not Guid?
Hi,
I have a MBA and I need to support 2 types of release
1. Which warn the user if a previous version exists and ask him to remove it
from ARP first
2. Removable patch
I have couple questions
1. I am not sure where and if I need to use RelatedBundle….
Action=quot;Patchquot;/ in MBA
2. How
After trying several variations I ended where you have. With common components
in a single MSI that goes with several bundles.
-Original Message-
From: Nicolás Alvarez [mailto:nicolas.alva...@gmail.com]
Sent: Wednesday, October 02, 2013 12:29 PM
To: General discussion for Windows
Thanks for the info and tips. This brings me to another post of mine here
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-to-handle-a-context-menu-component-on-install-upgrade-td7589322.html
. I asked if it was possible to update a context menu handler component
without
Reboot, since it's 100% effective.
In a multi-user environment, you wouldn't want to be killing everyone's shell
off (if it were even possible). If it were me, I wouldn't force the reboot
either. (Similar to how TortoiseGit upgrades happen; I can ignore the reboot
till it suits me.)
Кирилл отправил вам сообщение. Прочитайте его до того, как оно будет удалено!
Чтобы прочитать сообщение, перейдите по этой ссылке:
http://eu1.badoo.com/0340187522/in/Qt0-7fKkri4/?lang_id=2g=57m=65mid=524ce46a0002025d516a00ec4054016c
Если ссылка не работает, скопируйте и вставьте её
Yeah, IMHO, bundles are the future of MSI packages, somewhat captured here:
http://robmensching.com/blog/posts/2012/6/25/b-is-for-bundle-and-thats-good-enough-for-me
On Wed, Oct 2, 2013 at 2:03 PM, Wheeler, Blaine (DSHS/DCS)
bwhee...@dshs.wa.gov wrote:
After trying several variations I ended
38 matches
Mail list logo
