I dont't know why you keep asking the reason to create msu file instead of
telling what to do.
Obviosly, it is necessary to integrate the windows 6.x updates using rt
seven lite.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/how-to-create-a-MSU-
I dont't know why you keep asking the reason to create msu file instead of
telling what to do.
Obviosly, it is necessary to integrate the windows 6.x updates using rt
seven lite.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/how-to-create-a-MSU
Wix custom actions that are affected by the XP SP2 requirement are all
contained in extensions, and you can see if any of those extensions may have
added any of these custom actions by looking in the Source column of the
CustomAction table for values prefixed with "Wix", "IIs", "Sca", "NetFx", o
> MSIs created by WiX toolset will run fine (as long as you target Windows
> Installer that supports Win2k).
> However, any WiX code that gets carried with your MSI (like custom actions or
> Burn) require WinXP SP2+.
Looking at the verbose log files it looks as though some custom actions must be
Which timestamp? Creation time, or Modification time?
> From: ruth...@intergraph.com
> To: wix-users@lists.sourceforge.net
> Date: Thu, 27 Jun 2013 18:18:29 +
> Subject: [WiX-users] timestamp of dlls is not right in wix installation
>
> Hi,
> We got an issue about wix installation:
> We inst
XSLT?
The -var argument is expected to be a variable that points to the directory
that is the argument to the dir argument.
One option might be to change -var wix.IntelaTracPath to be -var
var.IntelaTracPath.de and change your commandline to candle.
If calling candle via a wixproj file, add
1. Is the empty folder inside the GAC or in your product's directory tree? If
the later, you could try adding a RemoveFolder element to your component. The
former would be a fusion bug.
2. If you need to show UI from ARP, you would need to add to your MSI, which would combine the "Change" and
I have verified that setting that WixVariable is what is controlling the
language that is displayed. If I switch to fr-CA Regional Settings but I have
English.wxl as the value of that variable, The .NET installer displays in
English. If I have en-US as my regional settings but I have French.wx
There are several people on this list who might be convinced to write such a BA
(and possibly even contribute it back to WiX) if their time were compensated.
Just sayin' ;-)
> From: r...@robmensching.com
> Date: Thu, 27 Jun 2013 10:35:34 -0700
> To: wix-users@lists.sourceforge.net
> Subject: Re
That would be awesome if it is true. I will try it out tomorrow and thanks!
From: Hoover, Jacob [via Windows Installer XML (WiX) toolset]
[mailto:ml-node+s687559n7586933...@n2.nabble.com]
Sent: Thursday, June 27, 2013 12:53 PM
To: Mark Van Dyke
Subject: Re: Burn - Localization Identifiers Duplic
Very plausible. My understanding is that basically Restart Manager sorts
processes into three groups: services (which it can see either have explicit
stop commands in the MSI or not), applications in the same desktop that have a
visible window with a title (to which it can send messages to shut
Wow, look, I'm self consistent system (at least in email). Not bad for a
human, eh?
On Thu, Jun 27, 2013 at 9:46 AM, Nick Ramirez wrote:
> I think you're right. This other thread seems to agree:
>
> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Installl-upgrade-several-MSIs-in-
I think you're right. This other thread seems to agree:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Installl-upgrade-several-MSIs-in-one-single-transaction-td7495903.html
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bootstrapp
Burn is only used when you create a Bundle. Any version of the WiX toolset
can target any version of the Windows Installer so I recommend using the
latest version, v3.7.
On Thu, Jun 27, 2013 at 1:23 PM, Andrew Jones wrote:
> > MSIs created by WiX toolset will run fine (as long as you target Wind
I haven't looked into this myself, but I can't imagine how it would be
automatically translated, so I'm guessing you would have to do localization
yourself.
-Original Message-
From: TimM [mailto:timmay...@smarttech.com]
Sent: June 27, 2013 17:28
To: wix-users@lists.sourceforge.net
Subje
This may be a simple question, but with Wix we get this free MajorUpgrade
with Downgrade element, which is great:
My question is if we support multiple languages and if on another language
OS we perform an install that is a downgrade will we automatically get this
downgrade message transl
Ohh that is it!
I didn't know about the Visible attribute.
Thank you very much
2013/6/27 Alain Forget
> If you're using Burn, wouldn't you just be able to set the MsiPackages'
> Visible attribute to yes, and Permanent to yes (so that all the packages
> aren't automatically uninstalled if the B
> MSIs created by WiX toolset will run fine (as long as you target Windows
> Installer that supports Win2k).
> However, any WiX code that gets carried with your MSI (like custom actions or
> Burn) require WinXP SP2+.
I assume it must be Burn as I don't have any custom actions. To get something
If you're using Burn, wouldn't you just be able to set the MsiPackages' Visible
attribute to yes, and Permanent to yes (so that all the packages aren't
automatically uninstalled if the Bundle is uninstalled)?
-Original Message-
From: nianderneves [mailto:niander.ne...@gmail.com]
Sent: J
Hello,
Can I generate separate entries in Add/Remove for each MSI that my bundle
installs?
The bundle just put a reference for him in Add/Remove.
I want that my bundle put a a reference for him in Add/Remove and also a
reference for each MSI that the bundle instaled. The bundle would give the
opt
Over the next couple days, we're going to be doing some upgrades to the
http://wixtoolset.org infrastructure. As a result the website will probably be
up and down and all around. Apologies in advance for any issues this might
cause you.
---
I have just confirmed that, when my service is running the cmd.exe process, the
RestartManager requests the restart, while otherwise, it does not.
My service would immediately kill the cmd.exe process the moment the service is
asked to stop, but for whatever reason, I'm guessing the RestartManag
MSIs created by WiX toolset will run fine (as long as you target Windows
Installer that supports Win2k).
However, any WiX code that gets carried with your MSI (like custom actions
or Burn) require WinXP SP2+.
On Thu, Jun 27, 2013 at 12:36 PM, Andrew Jones
wrote:
> Am I right in assuming that an
Am I right in assuming that an installer created with WIX 3.7 will not run on
Windows 2000? Did V3.6 create installers that will run on Windows 2000? Can you
have both 3.6 and 3.7 installed at the same time?
Andrew
--
T
I know 2 is by design. If a user selects uninstall from ARP, then they
shouldn't go into maintenance mode with an option to repair/etc. I don't use
the GAC so I can't comment on 1.
-Original Message-
From: Lu, Jie (Ruth) [mailto:ruth...@intergraph.com]
Sent: Thursday, June 27, 2013 1:1
I think the intent would be to have a "Preqba.wxl". Have multiple files with
the same name in LCID specific sub folders.
So,
http://example.com/license.html";
LogoFile="path\to\customlogo.png"
/>
...
Hi,
We got an issue about wix installation:
We installed our dlls into GAC. The timestamp of dlls show the installation
date instead of package/build date, which will cause the future problems of our
product. Is there any way to keep the package time?
Thanks
Ruth
Hi,
I got a couple of problems of wix uninstall:
1. Our dlls are installed in GAC. When we upgrade to .Net 4.5, uninstall
remove the dlls in the GAC, but still left the empty folders there, is it a
bug? Is there any way to remove the folder also? In .Net 4.0, there is no such
problem (
Sorry for the delay. I'm not sure I want non-elevated privileges to be able to
stop my service, but I suppose that might be a last-ditch solution. Also, I
thought for that CAs had to be marked as deferred (rather than immediate) for
them to be quietly/silently executed in the background...is th
Hey! Thanks! The compiler error is gone.
I was in the middle of putting together an example for this because what is out
there on this issue is very sparse and I haven't been able to find a
"start-to-finish" example. However, in putting all the pieces together, I
realized something and now I
Dear All,
I am using the command below to generate the .xml file:
heat.exe dir "%SrcRootDir%\de" -cg IMC_DE -ag -scom -sreg -sfrag -dr
IntelaTrac -var wix.IntelaTracPath -out "%CleintPrjDir%\IMC_DE.wxs"
And part of the result of the command is displayed below:
http://schemas.microsoft.com/wi
Bug http://sourceforge.net/p/wix/bugs/2766/ captures some of the relevant
issues. This is a very hard problem to solve correctly in Burn (think about
all the scenarios for a while and you'll see how deep the rabbit hole
goes). Multi-MSI Tx is a reasonable way out if it worked reliably (our
tests sh
Jacob, exactly right and that's just the beginning. We saw strange behavior
in early tests based on whether you installed a 32-bit or 64-bit MSI
package before the other (I forget the order). There are all kinds of
subtle issues that start coming out.
I have an old motto: If neither Office nor Vis
That's reasonable too.
I've considered creating such a thing before but it's not particularly
interesting problem for me so it's not a place where I'd choose to invest
my volunteer time.
On Thu, Jun 27, 2013 at 10:25 AM, Alan Fors wrote:
> That's a reasonable statement Rob. It would be nice,
This would get ugly if you had mixed bundles with other installers (Exe
packages from 3rd parties).
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: Thursday, June 27, 2013 12:17 PM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users]
That's a reasonable statement Rob. It would be nice, however, if there was a
simple prerequisite BA packaged with WiX. I'd like to do the same as Shay is
requesting, without needing to write a custom BA, or re-crafting the MSI UI in
the wixstdba.
Alan
-Original Message-
From: Rob Mensc
Not today. Multi-MSI Transaction API was buggy (that's why you don't seen
major Microsoft products using it). We should eventually add it as an
opt-in feature to Burn at some point so that if your MSIs can handle it
Burn will support it.
On Thu, Jun 27, 2013 at 10:01 AM, Phil Wilson wrote:
> Th
It is possible however you'd need to write a custom BA. The wixstdba
(provided with the WiX toolset) is designed to create a "single
installation experience" not "bunch of independent installs popping up".
On Thu, Jun 27, 2013 at 2:48 AM, Vinoth M wrote:
> I think this is not possible with WIX
Wesley
I filled in the unsubscribe form on the website for you, you need to reply to
that email (not this one) and you will be unsubscribed.
Dave
-Original Message-
From: Wesley Wells [mailto:wwe...@midsouthmetalsupply.com]
Sent: 27 June 2013 17:00
To: 'General discussion for Windows In
The patch certificates go in the wix for your original msi.
Then you use signtool to sign that msi and any patch msp that you create.
If you have already released your MSI then you will either need to re-release
it as a major upgrade to include the embedded certificate or release a patch
with the
Look at the Bootstrap Manifest Generator - that's the customizable Visual
Studio bootstrapper.
Phil
-Original Message-
From: Blair Murri [mailto:os...@live.com]
Sent: Thursday, June 27, 2013 5:07 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Is
This is the problem that a single transaction over multiple MSI installs can
solve. At the risk of stating the obvious, the transaction (a.msi+b.msi) is
not committed until b.msi is successful. The failure of b.msi will roll back
b.msi AND a.msi, and the rollback of a.msi will reinstall the older v
Thanks Jacob and Blair
By changing the custom-action attribute to Impersonate="no" from "yes" is
resolved my issue. But Signing the MSP is very important thing for patch
installation.
I am not able to sign the msp as Jacob suggested, because I unable to add
the PatchCertificates to my patch.wxs.
>Are the components that are flagged by those two ICE warnings coming from the
>MSM or from the MSI consuming it?
The components are in the MSM but the warnings appear when building the MSI
>What resources are in the components producing the ICE 57 warnings?
It is just one component (gene
I Just talked to Wix and they were supposed to unsubscribe me to all these
emails!!!
-Original Message-
From: Nicholas Pierce [mailto:nicholas.pie...@permasense.com]
Sent: Thursday, June 27, 2013 10:50 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] S
Just write the version number, with a v in front and no quoting
(i.e. SQL_SERVER_VERSION >= v10.50).
Nicholas
On 27 June 2013 16:06, snowkoan wrote:
> Cool. So we have a Burn variable called SqlCe40Version, that contains a
> version string like "14.0.0.0"
>
> How can we do a version comparison
Cool. So we have a Burn variable called SqlCe40Version, that contains a
version string like "14.0.0.0"
How can we do a version comparison with a hardcoded string, like
"v4.0.8876.1"
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/SQL-CE-4-0-Packag
We are using BURN and have developed our entire installer UI using C++ / MFC.
For non-admin users who are installing our product, we would NOT want them
to navigate through our entire BURN UI Dialog sequence and then finally
click on the "Install" button, to get the UAC prompt; and then realize th
1.Are the components that are flagged by those two ICE warnings coming from the
MSM or from the MSI consuming it?What resources are in the components
producing the ICE 57 warnings?What are the "default" paths of the
directories producing the ICE 91 warnings? HKCU is per-user registry dat
Another possibility is the Visual Studio Bootstrapper.
> From: vino...@eurofins.com
> To: wix-users@lists.sourceforge.net
> Date: Thu, 27 Jun 2013 09:48:13 +
> Subject: Re: [WiX-users] Is it possible to have a bundle without a UI?
>
> I think this is not possible with WIX Bootstrapper. Pleas
Question 1.
I am creating an MSM for a COM DLL. I am using the MSM in my own per-user MSI
and I am getting ICE warnings 57 ("per-user and per-machine data with an HKCU
Registry KeyPath") and 91 ("file will be installed to the per user directory
that doesn't vary based on ALLUSERS "). How do I fi
I think this is not possible with WIX Bootstrapper. Please find my answer in
stack overflow for the same requirement.
http://stackoverflow.com/a/17043234/1124244
-Original Message-
From: Shay Friedman [mailto:shay.fried...@gmail.com]
Sent: Thursday, June 27, 2013 2:42 PM
To: wix-users
Some people have had success using Burn. Search this mailing list for the word
DisplayInternalUI as it has been discussed several times.
> Date: Thu, 27 Jun 2013 12:11:56 +0300
> From: shay.fried...@gmail.com
> To: wix-users@lists.sourceforge.net
> Subject: [WiX-users] Is it possible to have a b
Hi,
I've created an installer using WIX and it works fine. Now I want to add a
prerequisite installer that installs .NET before the actual installer jumps
in.
The thing is that I don't want UI for this bootstrapper... I want something
like the following flow:
- Check if .NET is installed
- if not,
54 matches
Mail list logo
