Neil and Phill,
I believe I've added enough to address both of these issues. Go to:
http://wixtoolset.org/issues/edit/me
There you should be able to update your username (and full name and email*)
as well as re-send the activation email. I've also fixed the DNS records.
The wixtoolset.org was mis
My bundle needs to perform a conditional install if a 3rd party program
if the version installed is none or less than a particular version.
The problem is the 3rd party program stores the installed version number
in a dynamic guid section of HKLM, so I don't have a deterministic path
to the inform
VS 2013 has "Go Live" license, it would be nice to have WiX support.
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: Thursday, July 25, 2013 10:58
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] VS 2013 support
And since I w
Does this ever work or is it failing consistently? If it's intermittent
then unreliable access to that location could still be the cause.
One other question is what does D: map to? You mention network, which makes
me wonder if this is a mapped drive. Does this work if you use an entirely
local pat
Never mind, it clearly does, given the LGHT error.
Maybe the extra backslash is confusing it? i.e., maybe
$(var.KMI.IntelliDrive.ServicesHost.TargetDir)\KMI.IntelliDrive.ServicesHost.vshost.exe.config
Should be
$(var.KMI.IntelliDrive.ServicesHost.TargetDir)KMI.IntelliDrive.ServicesHost.vshost.e
Might be related to: http://wixtoolset.org/issues/3643/
On Fri, Aug 23, 2013 at 3:24 AM, Bruce Cran wrote:
> I seem to have managed to get Burn rather confused. I have an MSI
> package with new product and upgrade codes in version 2.0 due to
> different builds being produced. I ask Windows Inst
You may already have verified this, but are you sure
$(var.KMI.IntelliDrive.ServicesHost.TargetDir) is defined and points to the
location you think it's supposed to point to?
Alain
-Original Message-
From: Bodden, Doug (KMWCR) [mailto:doug.bod...@kantarmedia.com]
Sent: Friday, August 2
I'm seeing a LGHT0103 error. The files are simply reported as not found;
but they're there. If you look at the light.exe command I ran below - I
grabbed the command text from a Visual Studio build log, and then ran
the ls command in powershell immediately after to demonstrate that the
file is there
Ah, in that case, the only way would be to do a silent install with the msiexec
command, and there would be no way to complete hide that window in WiX, correct?
-Original Message-
From: Wesley Manning [mailto:wmann...@dynagen.ca]
Sent: Friday, August 23, 2013 14:23
To: afor...@cmu.edu; G
SharedDllRefCount once is set to "yes", you should not change it ever. The
reason of course, you have dll out on the customer site using the older
version that will have conflicting issue.
You can set it to "no", but you need to write a custom action that will set
the SharedDllRefCount to 1 as a
There's the VersionNT64 property. It's undefined on 32 bit systems.
On 23/08/2013 2:43 PM, Brian Payne wrote:
> Property VersionNT
>
> http://msdn.microsoft.com/en-us/library/windows/desktop/aa370556(v=vs.85).aspx
>
> For 32/64 bit detection, write a custom action and set a Public Property.
>
>
>
If you do that in the UI sequence, you won't get the file on a silent install.
You probably meant as an immediate action.
Dave
From: Brian Payne
To: General discussion for Windows Installer XML toolset.
Sent: Friday, August 23, 2013 11:59 AM
Subject: Re:
2013/8/23 ak m :
> Dear All,
>
> How to create OS specific installer using Wix?
>
> For Example,
>
> Installer created for Windows XP 32-bit, should install on Windows XP
> 32-bit only.
> Installer created for Windows Vista 32-bit, should install on Windows Vista
> only 32-bit.
>
>
> OS: XP, Server
See if this helps:
http://blogs.msdn.com/b/heaths/archive/2009/04/12/patch-applicability.aspx
Phil Wilson
On Thu, Aug 22, 2013 at 3:47 AM, Swaroop Kare
wrote:
> Hi,
>
>
>
>I am able to make Patch1 based on
> http://wix.tramontana.co.hu/tutorial/upgrades-and-modularization/patchwo
> rk but
Write a Custom Action (CA) in the UI sequence, the CA contained the
embedded resource of the INI file for you to write out.
If you're doing that in a Windows .DLL file, here is one way to do it:
HRSRC hRCStub;
DWORD dwStubSize;
HGLOBAL hGBStub;
char *pStubData;
FILE *fOut;
char szOutFile[MAX_PATH]
Exactly where is this ini file? It doesn't sound like it's actually
packaged in the MSI file. Do you actually need the ini file or just the
model number out of it?
There's the DiFX framework for installing drivers - that might be useful.
http://msdn.microsoft.com/en-us/library/windows/hardware/f
There are some caveats. I'm pretty sure you need MSI 4.5, and you can't add
msidbComponentAttributesShared in the patch - it needs to be in the
original product install, in case you're doing that.
Phil Wilson
On Fri, Aug 23, 2013 at 6:24 AM, william lee wrote:
> Hi,
> uninstalling a msp, I fo
I forget what the DropBox install experience was, but when I look at those
shell extensions they are all in HKCU, so they are per-user and not
per-system. That might work for you too.
Phil Wilson
On Fri, Aug 23, 2013 at 1:59 AM, Trond Andersen wrote:
> I have an application which uses Shell ext
Property VersionNT
http://msdn.microsoft.com/en-us/library/windows/desktop/aa370556(v=vs.85).aspx
For 32/64 bit detection, write a custom action and set a Public Property.
On Fri, Aug 23, 2013 at 4:59 AM, ak m wrote:
> Dear All,
>
> How to create OS specific installer using Wix?
>
> For Examp
Technically that dialog is not part of MSI, its part of OS msiexec.
-Original Message-
From: Alain Forget [mailto:afor...@cmu.edu]
Sent: August-23-13 2:59 PM
To: 'Bruce Cran'; 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] [Wix]: Create silent MSI using W
When I was following the tutorial, I don't remember seeing anything. That said,
maybe the installation was so brief that it didn't display. In a heavier
installer, you may be right that some kind of progress bar (maybe with a cancel
button) displays.
Alain
-Original Message-
From: Bruc
On 23/08/2013 15:20, Alain Forget wrote:
> Don't WiX-built MSIs have no UI by default?
>
> See the second paragraph of
> http://wix.tramontana.co.hu/tutorial/user-interface
>
> So just follow the steps of the Getting Started tutorial, and don't do
> anything in the UI section?
I think there's a
In order to show a dialog you need to pause the engine thread
one why to do it is to use some kind of a mutex
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-managed-UI-how-to-cancel-and-rollback-tp7577071p7588377.html
Sent from the wix-use
Dear All,
when user clicks MSI,
1. Copy the INI file to local temp folder before Install Files action (MSI
action)
2. Get the model information from INI
3. Install the printer driver
Could any one help me on this?
Thanks in Advance...
Anil
---
Don't WiX-built MSIs have no UI by default?
See the second paragraph of http://wix.tramontana.co.hu/tutorial/user-interface
So just follow the steps of the Getting Started tutorial, and don't do anything
in the UI section?
-Original Message-
From: ak m [mailto:wixak...@gmail.com]
Sent
Dear All,
How to create silent MSI?
For Example,
When user click MSI, it should not display any UI.
For your Information, I know how to install the MSI from Command line
silently.
Could any one help me on this?
Thanks in Advance...
Anil
--
Also,
http://msdn.microsoft.com/en-us/library/aa370905(v=vs.85).aspx#operating_system_properties
For example, to tell the difference between server and workstation editions
of Windows, you can use MsiNTProductType.
On 23 August 2013 13:58, Pally Sandher wrote:
> http://msdn.microsoft.com/en-u
Hi,
uninstalling a msp, I found shared components files downgrade to original
version.
such shared components have ref counting and msidbComponentAttributesShared.
it should keep highest version when other product also refer it, as
promised by msidbComponentAttributesShared attribute.
I inspect th
http://msdn.microsoft.com/en-us/library/windows/desktop/aa368012.aspx
http://msdn.microsoft.com/en-us/library/aa372495.aspx
http://msdn.microsoft.com/en-us/library/aa372497.aspx
Palbinder Sandher
Software Platform Engineer
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**
Dear All,
How to create OS specific installer using Wix?
For Example,
Installer created for Windows XP 32-bit, should install on Windows XP
32-bit only.
Installer created for Windows Vista 32-bit, should install on Windows Vista
only 32-bit.
OS: XP, Server2003, Vista, Server2008 7, 8, Server20
I seem to have managed to get Burn rather confused. I have an MSI
package with new product and upgrade codes in version 2.0 due to
different builds being produced. I ask Windows Installer (in the MSI) to
upgrade from the previous one with:
Snippet
NOT OTHER_PRODUCT_INST
I have an application which uses Shell extensions to add a menu in Windows
Explorer, however I would like the installer to have a fallback if the user
is not able to give the installer admin rights in which the user can access
the functionality without using menus/toolbar in Windows Explorer. The
D
Hi Blair,
I'm preparing a test file with as less as possible, in the mean time, I got a
different error runing my script as admin. I'm posting here and hope it helps,
>>
torch.exe : error TRCH0001 : Index and length must refer to a location within
the string.
Parameter name: length
Exception Ty
33 matches
Mail list logo
