I am WELL aware of the following:
1) You should always have an upgrade code, even if you don't plan on
upgrading. But for this specific product, I am positive I do not want the
upgrade code. We will never support an upgrade for this product, due to other
incredibly obnoxious
-Original Message-
From: Scott Ferguson [mailto:scott.fergu...@a2ktechnologies.co.nz]
Sent: Monday, May 11, 2015 12:21 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Per-User Previlage To Write to Program Files
Not sure about the internal filters that
On 2/26/2015 5:18 AM, Phill Hogland wrote:
What do you have Product/@InstallerVersion set too?
This link http://support.microsoft.com/kb/305496 indicates that you
need to install the Windows Installer 2.0 redistributable to support a
Product/@InstallerVersion='200', but the link to the
- Original Message -
From: Hoover, Jacob jacob.hoo...@greenheck.com
To: General discussion about the WiX toolset.
wix-users@lists.sourceforge.net
Cc:
Sent: Friday, February 13, 2015 3:04 PM
Subject: Re: [WiX-users] Using a WiX Selection Tree control, when I select
Feature 1, I
or anyone has any other ideas.
-Original Message-
From: David Connet [mailto:d...@agilityrecordbook.com]
Sent: Friday, February 13, 2015 3:14 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Using a WiX Selection Tree control, when I select
Feature 1, I want
On 2/11/2015 5:02 AM, JohnLudlow wrote:
Hi,
On a Windows Server 2003 RTM machine, launching our bundle (which has a
custom managed BA) yields this error:
/ The procedure entry point DecodePointer could not be located in the
dynamic link library KERNEL32.DLL.
/
On 1/22/2015 10:33 PM, sky wrote:
I'm now using burn cumstom bootstrapper application, and in my custom ba
there is a step for validating product key. But since my msi file is
external to the bootstrapper, anyone can install msi file directly without
entering a product key. How can I prevent
- Original Message -
From: Phil Wilson phildgwil...@gmail.com
To: General discussion about the WiX toolset.
wix-users@lists.sourceforge.net
Cc:
Sent: Friday, December 12, 2014 11:30 AM
Subject: Re: [WiX-users] Windows Updates - either pending or running causes
our installs to
Another approach would be to just throw up your hands and say I can't
upgrade from that. Force the users to uninstall before your install.
Then the old version is removed. And the new one comes in cleanly.
Assuming the old one uninstalls cleanly! Very user-hostile however...
Dave
On
On 11/19/2014 2:37 AM, jason.small...@bt.com wrote:
I have looked more closely at the logs and if I try to open the file
I want to change at the point Before=InstallFinalize, then the file
does not exist. If I use After=InstallFinalize then I can open the
file but I don't have permission to
After a lot of advice from this group, I implemented some functionality where
I
encrpyt part of a file that is installed. I do this with a deferred custom
action.
Now it won't uninstall. If I remove the custom action then it uninstalls.
That's not surprising. When you modify a file
The problem is that your CA is immediate. So when you run, the file hasn't been
installed yet - they're installed during the deferred phase.
Dave
From: jason.small...@bt.com jason.small...@bt.com
To: wix-users@lists.sourceforge.net
Sent: Tuesday, November 18, 2014 9:26 AM
Subject:
if i provide install and a rollback, who will revert the system changes,
that were made during install, while un-installing?
When I've had to do this, usually only 2 CAs are needed: install and uninstall.
Rollback during an install is an uninstall.
Similarly, rollback during uninstall is an
On 7/6/2014 10:57 AM, Dolevo Jay wrote:
Hi,
I have an installer in WIX. I have tried to deploy it to a group of target
computers in the network and encountered the following issue. The deployment
was successful but there is an issue when the installer launches the
application after the
I have:
UpgradeVersion
OnlyDetect=yes
Minimum=$(var.CURRENT_VERSION)
IncludeMinimum=yes
Maximum=$(var.CURRENT_VERSION)
IncludeMaximum=yes
Property=SAMEVERSIONDETECTED /
CustomAction Id=MyAlreadyUpdated
Meant maybe try to explain why you are getting downgrading between builds
with no errors - from 2.3.4.6 to 2.3.4.2 Got ahead of myself.
As far as MSI is concerned, those 2 version numbers are the same. MSI only
looks at the first 3 parts.
I just did this and it was pretty painless. Only had to make one change to my
wxs - remove the 'Action=create' attribute from my RegistryKey element.
Dave
From: Heath Stewart hea...@outlook.com
To: General discussion for Windows Installer XML toolset.
From: Rob Mensching r...@firegiant.com
To: General discussion about the WiX toolset.
wix-users@lists.sourceforge.net
Sent: Wednesday, May 21, 2014 3:55 PM
Subject: Re: [WiX-users] [WiX-devs] Query- Wix 3.5 integration with VS 2013
And that technically isn't necessary. You'll just get a
TARGETDIR is not what you use to set the install location.
You want to replace your Id 'Root' with something like INSTALLDIR. That's the
variable you set on the command line. Additionally, you need to set
Feature/@ConfigurableDirectory to INSTALLDIR.
And to deal with repair/upgrades, you need
You can use the UpgradeVersion elements if you want (I do - I have different
error messages for same-version and new-version already installed). The key is
that the product id must change. What DavidW suggests (*) works nicely.
DaveC
From:
On 3/20/2014 6:32 AM, sergey.s.be...@yandex.ru wrote:
why not jscript or vbscript inline custom actio
http://blogs.msdn.com/b/robmen/archive/2004/05/20/136530.aspx
Dave
--
Learn Graph Databases - Download FREE O'Reilly
Be aware, if you write those values back into the MSI, then you just
invalidated the digital signature. The MSI will have to be re-signed.
MSI is just a database, so you can easily write a script to update it. You can
also edit the MSI with Orca (or my favorite, InstEd).
Now the (weird) thing
This will only work on Windows Installer 5.0+.
You need to set ALLUSERS=2 and MSIINSTALLPERUSER=1
Dave
On 2/18/2014 1:37 AM, Thomas Brodersen wrote:
I am trying to create a perUser installation package for an application that
will install to the ProgramFilesFolder (which should be something
On 2/10/2014 8:22 PM, Chetan Rajakumar wrote:
Hi Dave,
Can you please let me know what all changes you are making for this.
Please let me know what code you are writing in python script, Is this Script
placed in Wix Installer project?
How you are setting command line parameters which u pass
On 2/10/2014 5:48 AM, Chetan Rajakumar wrote:
Hi All,
Below is my requirement:
I have a Version.txt file kept under WixInstaller project and I have below
text in Version.txt:
BuildVersion=1.2.3.4
Now I have to read the above BuildVersion from the Version.txt and Update the
value of
...@verizon.net wrote:
It knows about our custom actions as well and they rollback just fine.
On 02/06/2014 09:42 PM, David Connet wrote:
I have to wonder, why in the world are you using cmd.exe in a custom
action to copy a file? (**twitch** **twitch**)
CopyFile is much easier and msi knows about
I have to wonder, why in the world are you using cmd.exe in a custom
action to copy a file? (**twitch** **twitch**)
CopyFile is much easier and msi knows about it (hence handles
uninstall, rollback, upgrade, etc).
Dave
On 2/6/2014 5:35 PM, Gerry Reno wrote:
Ok, after some experiments:
The
The other thing to watch for - based on the file name, it looks like
you're trying to run an installer. If that is MSI-based, you can't do that.
And I'd be a little concerned about your requirement to run in the
foreground. What happens if the installation is run as silent (no UI)?
Dave
On
The upgrade table works very nicely for this. Error out on same-version. In my
upgrade table I have:
UpgradeVersion
OnlyDetect=yes
Minimum=$(var.CURRENT_VERSION)
IncludeMinimum=yes
Maximum=$(var.CURRENT_VERSION)
From: Gerry Reno [mailto:gr...@verizon.net]
Binary Id='CMDEXE' SourceFile='C:\WINDOWS\System32\cmd.exe' /
I don't think that's legal. cmd.exe is not a redistributable file. You
can't include it in your installer.
And if you're building a 32-bit msi on an x64 system, it will definitely
/2013 10:44 AM, David Connet wrote:
From: Gerry Reno [mailto:gr...@verizon.net]
Binary Id='CMDEXE' SourceFile='C:\WINDOWS\System32\cmd.exe' /
I don't think that's legal. cmd.exe is not a redistributable file. You
can't include it in your installer.
cmd.exe is not being distributed
From: Gerry Reno gr...@verizon.net
To: wix-users@lists.sourceforge.net
Cc:
Sent: Friday, December 20, 2013 10:42 AM
Subject: Re: [WiX-users] ExeCommand will not accept any path with spaces
On 12/20/2013 01:20 PM, David Connet wrote:
From: Gerry Reno gr...@verizon.net
To: wix-users
There is no way (that I know of) to delete a directory where something
has an open handle on that. The only way is to make sure all programs
have stopped and no open programs have that as their current directory.
It's just like opening cmd.exe, cd'ing to a directory and trying to
delete that
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 beekeeper2...@gmail.com
To: General discussion for Windows Installer XML toolset.
Or before InstallInitialize. REP must be within the install transaction.
Dave
From: Phil Wilson phildgwil...@gmail.com
To: afor...@cmu.edu; General discussion for Windows Installer XML toolset.
wix-users@lists.sourceforge.net
Sent: Monday, August 19, 2013
![CDATA[VersionNT64 OR $(var.Platform) = x64]]
That doesn't make much sense because $(var.Platform) is compile time. For an
x64 build, it's like you wrote:
![CDATA[VersionNT64 OR x64 = x64]]
(and x86 is ![CDATA[VersionNT64 OR x86 = x64]])
This could be simplified to VersionNT64
Dave
Assign them to a feature and condition the feature.
Dave
- Original Message -
From: Steven Ogilvie steven.ogil...@titus.com
To: General discussion for Windows Installer XML toolset.
wix-users@lists.sourceforge.net
Cc:
Sent: Tuesday, July 30, 2013 7:16 AM
Subject: Re: [WiX-users] Need
Maybe because GetVersionEx lies for a certain class of programs (installers).
And for all programs on Win8.1 unless you specifically manifest that you
support 8.1.
http://msdn.microsoft.com/en-us/library/windows/desktop/ms724451%28v=vs.85%29.aspx
provides some details in the user comments...
And make sure the phView is actually pointing at a view handle. Usually,
you'd have
MSIHANDLE hView;
...
If (MsiDatabaseOpenView(database, SELECT 'Data' FROM 'Binary' WHERE
'Name'= 'Hasp', hView) != ERROR_SUCCESS)
...
Dave
On 11/22/2012 9:19 AM, Peter Shirtcliffe wrote:
Adjust that to
That's not valid XML. You need to either put the condition in a CDATA block or
use the gt; entity.
Dave
From: Bill Pierce bpie...@beyondtrust.com
To: wix-users@lists.sourceforge.net wix-users@lists.sourceforge.net
Sent: Tuesday, June 26, 2012 9:50 AM
Make sure your DLL is statically linked. It may be failing because a dependent
dll (that you're installing - for instance vc runtime) does exist yet.
Dave
From: Joe Damato j...@boundary.com
To: General discussion for Windows Installer XML toolset.
And be prepared for domain users to have paths like N:\
(HOMEDRIVE=N: HOMEPATH=\)
Dave
On 5/23/2012 9:31 AM, Peter Shirtcliffe wrote:
Remove the registrysearch and add
SetDirectory Id=HOMEPATH Value=[%HOMEDRIVE][%HOMEPATH] /
-Original Message-
From: Daniel DA COSTA
If you sequence before InstallFinalize, you need to also schedule
InstallExecute (and REP is sequenced after that.)
http://msdn.microsoft.com/en-us/library/windows/desktop/aa371197%28v=vs.85%29.aspx
Dave
On 3/30/2012 1:40 PM, Wilson, Phil wrote:
There may not be enough context in that WiX to
In my installer, I set 2 ShortcutPropertys
System.AppUserModel.PreventPinning=0
System.AppUserModel.ID=myid
This works fine and enables the 'pin to' options on the shortcut.
Now, if I pin the both the taskbar and start menu and then uninstall the
program, only the start menu pinning is
Have you set the ConfigurableDirectory attribute on the Feature?
... Feature ... ConfigurableDirectory=INSTALLDIR ...
Dave Connet
On 08/04/2011 10:57 AM, Joe Tilley wrote:
I'm using WixUI_InstallDir as the installer UI, and it pops up with my
INSTALLDIR as the default directory as it
45 matches
Mail list logo
