Although making the appropriate shortcut during installation is the best answer
normally - If it isn't working this way could you create the per user shortcut
a different way after installation completes. Maybe Active Directory policy or
power shell during logon or
-Original
On the whole, an ini file is best created on the first run of the application.
This avoids the whole - user context and folder privilege challenge since ini's
often have user specific settings they should be stored per user and not per
application
-Original Message-
From: Lars
The key is the context installation is being executed in and where that context
has rights.
If you run elevated the install won't have access to your personal store. If
you run personal the install may not have access to the root store
-Original Message-
From: Roni Fuchs
Windows Installer can remove the bootstrapper for you. Use the Windows
Installer FindRelatedProducts action with the bootstrappers UPGRADECODE and
version.
-Original Message-
From: Mihailo Milenković [mailto:mihailo.milenko...@pstech.rs]
Sent: Monday, October 27, 2014 4:08 AM
To:
Should run.
Have a good weekend
Blaine Wheeler
Department of Social and Health Services
DCS IT Operations
360.664.5416
blaine.whee...@dshs.wa.gov
--
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Things that have bitten me in the past:
Is the same user ID doing the original install and the upgrade.
The user is not an admin
The HKLM key is per machine - the per user key would be under HKCU
The Windows installer service only recognizes 3 positions of version number
x.x.xxx
Or - get the specific VSTO version you built your bundle against and either
embed it in the bundle or provide your own download link
-Original Message-
From: darbid [mailto:davidbo...@gmx.de]
Sent: Thursday, May 08, 2014 2:28 AM
To: wix-users@lists.sourceforge.net
Subject: Re:
Can the answer be as simple as when you schedule RemoveExistingProducts?
Bob Arnson made this post on his blog that really helped me:
http://www.joyofsetup.com/2010/01/16/major-upgrades-now-easier-than-ever/
It includes a link back to MSDN
My experiences is the bootstrapper captures info on the signature or hash of
files it is to manage installation of. You have to assemble the content, up
the bootstrapper version number and re-compile every time any of the bundles
change.
This is a good thing as it ensures cohesion of
I get the same behavior from builds with both Wix 3,7 and 3.8
The only entry if ARP is for the bundle
Burn bundle 1.0 installs 2 msi packages.
Burn bundle 1.1 has 1 msi upgraded and leaves the other one unchanged. The
bundle is a MajorUpgrade and the upgrade code is unchanged.
I expect to see
After fighting the default OS locations I finally convinced others around here
that going with what the OS wants for directory structure is much simpler to do
and more stable and takes fewer steps of code.
I have a suggestion that may help and is more stable than a custom action.
Set a
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
Coincidentally I just read this section of Robert Dickau's tips page
http://www.robertdickau.com/msi_tips.html#unfix
-Original Message-
From: Simon Gerhold [mailto:simon.gerh...@cetis.si]
Sent: Wednesday, August 28, 2013 2:14 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users]
I'm not familiar with WixEdit but I use Heat frequently and find it to be very
solid. If you want the same output from both tools I'd go with Heat.
-Original Message-
From: Chaitanya Sanapala [PC-BLR-DEV] [mailto:chaita...@pointcross.com]
Sent: Tuesday, August 06, 2013 12:18 AM
To:
You can't do that.
-Original Message-
From: Parkes, Kevin [mailto:kevin.par...@wacom.eu]
Sent: Wednesday, July 17, 2013 9:02 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] DirectorySearch
I need to install a file into the 64-bit Program Files folder from a 32-bit MSI.
I
We have about 20 fragments with MSIPackages or EXEPackages in them. I need to
build several Bundles that have some of these Fragments in common. How can I
refer to them without actually having to add the wxs fragments to each Bundle
project. It would be handy to have 1 solution, with all of
or wixlibs.
--
John Merryweather Cooper
Build Install Engineer - ESA
Jack Henry Associates, Inc.®
Shawnee Mission, KS 66227
Office: 913-341-3434 x791011
jocoo...@jackhenry.com
www.jackhenry.com
-Original Message-
From: Wheeler, Blaine (DSHS/DCS) [mailto:bwhee...@dshs.wa.gov]
Sent: Friday
XP may be on its deathbed but some of us have to support it and will for quite
a while.
-Original Message-
From: David G. van Hoose [mailto:david.g.vanho...@gmail.com]
Sent: Tuesday, April 30, 2013 8:20 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re:
FYI - The Wix Toolset (3.7) still compiles msi and burn packages on XP with
either the command line tools or via VS2010.
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: Tuesday, April 30, 2013 10:54 AM
To: General discussion for Windows Installer XML toolset.
Why would you put a Payload element under an MSIPackage or an ExePackage?
Payload seems redundant when it's the child of one of the other elements,
particularly if the MSIPackage has the cab embedded in the msi file.
Blaine Wheeler
Department of Social and Health Services
Project Coordinator
for information on how to use it. There was also a recent discuss
on wix-devs about it.
On Tue, Mar 12, 2013 at 1:31 PM, Wheeler, Blaine (DSHS/DCS)
bwhee...@dshs.wa.gov wrote:
I want to create a self updating setup.exe with Burn. I hope that
using the Update element of the Bundle with Wix 3.7
information into there... however, IE renders ATOM really nicely, ala:
http://wixtoolset.org/releases/feed/v3.8
On Tue, Mar 12, 2013 at 1:31 PM, Wheeler, Blaine (DSHS/DCS)
bwhee...@dshs.wa.gov wrote:
I want to create a self updating setup.exe with Burn. I hope that using
the Update element
I want to create a self updating setup.exe with Burn. I hope that using the
Update element of the Bundle with Wix 3.7 will work. The Help says this
piece wasn't working yet but it looks like you use it for Wix updates. True?
Is there a reason you use a feed or was it just convenience?
My
The MSI documentation says that error 2109 mean Section missing for
.ini action
http://msdn.microsoft.com/en-us/library/aa372835(v=VS.85).aspx
There is probably a note higher up in the log that can tell you more
detail or at least the exact step
-Original Message-
From: Justin Hull
Do you have the IISExtension name space included at the top?
It should look something like this
?xml version=1.0 encoding=UTF-8?
Wix xmlns=http://schemas.microsoft.com/wix/2006/wi;
xmlns:iis=http://schemas.microsoft.com/wix/IIsExtension;
-Original Message-
From: Ulrich Peters
Congratulations
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: Monday, January 31, 2011 7:07 AM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] WiX v3.5 released!
WiX v3.5 Released! Tell your friends. Read more here:
It seems to me that the answer, and path you take lies in your audience.
If you have control of your systems I expect the XP machines already
have .Net 2 because so many applications require it. This gives you
the chance to poll the path/configuration managers and learn what they
have put in
Why not give your partner a merge-module or wixlib. That way he is can
control which version of your product goes with which version of his and
it solves the logo problem
Your build consumes the same thing you give the partner and then adds
your logo
-Original Message-
From: MeCoco
Choosing the drive with the largest available space is a function of the
Windows Installer, not Wix.
You can set the ROOTDRIVE property if you are certain where you
application should go.
http://msdn.microsoft.com/en-us/library/aa371372(v=VS.85).aspx
-Original Message-
From: Prabhat_IE
, Wheeler, Blaine (DSHS/DCS) wrote:
C:\delivery\Dev\wix35_public\src\ext\UIExtension\wixlib\ResumeDlg.wxs(18
) : error LGHT0197 : The Windows Installer XML variable
!(wix.WixUICostingPopupOptOut) is unknown. Please ensure the variable
is declared on the command line for light.exe, via a WixVariable
Candle succeeded but when I run light with the WixUIExtension I get this
error. I don't have a
c:\deliviery\Dev\Wix30_public\src\ext\UIExtension\wixlib folder on my
machine. Was there a problem with creating build 3.5.2020?
OutPut
Microsoft (R) Windows Installer Xml Linker version
Run the EXE and when the dialog displays - leave it open an search your
temp folder for the newest folder and files. The msi should be in there
someplace
-Original Message-
From: Wilson, Phil [mailto:phil.wil...@invensys.com]
Sent: Thursday, July 15, 2010 5:03 PM
To: General discussion
The ExecuteMode switch also helps a lot.
msiexec /I MySetup.msi /l*v log.txt ExecuteMode=None
-Original Message-
From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com]
Sent: Thursday, May 13, 2010 9:10 AM
To: General discussion for Windows Installer XML toolset.
Subject:
I just ran across this http://www.wix.com/
Blaine Wheeler
SEMS Operations
360.664.5416
The 'silly' question is the first intimation
of some totally new development.
Alfred North Whitehead
I don't think you'd get a downgrade you would like. I think you would
end up with a mush of the two slightly different versions of the
application because of the component versions.
Example:
V1 - has component 21 with ver 1.1.27
V2 - has component 21 with ver 1.2.0
You try to reinstall V1
Here is how we do it.
1. We had to get a 'code signers certificate'. There are many vendors;
Verisign, Thawte, Comodo or one of the competitors. If your company
already has a certificate, you are saved from much frustration. If not,
Comodo has very good instructions about installing the key
I'm trying to convert a VB6 msi build from Wise to Wix and ran afoul of
Heat and Tallow and trying to tell which of the Reg entries it extracts
matter to the wxs fragment.
Research led me to the June 07 thread in the Wix forum between
Richard.Foster, Neil Sleightholm, Mark Cheyne and
Another way is to install your utility with the msi, write a RunOnce
registry key with the command for the utility and then ScheduleReboot.
A dialog explaining the need to reboot to finish is nicer than
ForceReboot
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
I'd like to read your notes but unfortunately this link doesn't work for
me. http://john.mcfadyen.spaces.live.com
I concur with your views on Windows Installer and count myself very
lucky to build installs in a closed environment where we control the OS,
the installer on has to know 1 language
I use the well known user Authenticated Users in one of our products
and it seems to work fine. But we are in XP and I haven't had a chance
to see if it will work in
Vistahttp://www.dcs.dshs.wa.gov/dcs/semsops/prioritizationteam.asp
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
or log file. What are others doing?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of si
Sent: Thursday, March 06, 2008 12:26 AM
To: Wheeler, Blaine (DSHS/DCS)
Cc: WiX Users
Subject: Re: [WiX-users] Preventing upgrades for versions older than the
previous
My MSI works perfectly in the default but I can't figure out how to get
the msi to show a folder selection dialog to do an Admin install.
My command line says: msiexec.exe /a mymsi.msi
Do I have to author my own dialog or is there already one in the WIx
Source Files I can add using Publish?
42 matches
Mail list logo
