All,
I've got a customer who's getting an error when trying to install my
application, the installer of which was generated using Wix and Burn. From the
burn log, I can see the installer attempts to cache the bundle and the logs
reads thus
[1194:1198][2013-09-26T18:20:10]: Registering
.
On Thu, Sep 26, 2013 at 7:15 AM, Chris Lord chris.l...@atterotech.comwrote:
All,
I've got a customer who's getting an error when trying to install my
application, the installer of which was generated using Wix and Burn. From
the burn log, I can see the installer attempts to cache the bundle
virus checker's messing with Burn in
these scenarios but would be great to know for sure.
On Thu, Sep 26, 2013 at 7:15 AM, Chris Lord chris.l...@atterotech.comwrote:
All,
I've got a customer who's getting an error when trying to install my
application, the installer of which was generated
Why sir, surely if it is in verbal jousting that thoust taketh part, thou
should be sharpening thy lance and not thy sword.
- Original Message -
From: Rob Mensching r...@robmensching.com
To: General discussion for Windows Installer XML toolset.
wix-users@lists.sourceforge.net
Sent:
it Possible.
-Original Message-
From: Chris Lord [mailto:chris.l...@atterotech.com]
Sent: 08 November 2012 20:32
To: wix-users
Subject: Re: [WiX-users] Problem in Major upgrade
Chaitanya
Are both the original and the update installtion the same type? If one
is per-user and the other is per
Installer XML toolset.'
Subject: Re: [WiX-users] Problem in Major upgrade
Iam using wix 3.5
-Original Message-
From: Chris Lord [mailto:chris.l...@atterotech.com]
Sent: 07 November 2012 20:41
To: wix-users
Subject: Re: [WiX-users] Problem in Major upgrade
Chaitanya
What version of Wix
Chaitanya
What version of Wix are you using?
Chris
-Original Message-
From: Chaitanya [mailto:chaita...@pointcross.com]
Sent: Wednesday, November 07, 2012 4:43 AM
To: WiX-users@lists.sourceforge.net
Subject: [WiX-users] Problem in Major upgrade
Hi,
Iam trying to do major upgrade.
that, if you have a more specific question I am sure someone will
be able to answer it.
Chris Lord
Attero Tech, LLC
-Original Message-
From: Chaitanya [mailto:chaita...@pointcross.com]
Sent: Tuesday, November 06, 2012 9:19 AM
To: WiX-users@lists.sourceforge.net
Subject: [WiX-users
believe it or not, the write actually writes a DWORD even though you
ask it to write a string!!!
Hope this helps
Chris Lord
Attero Tech, LLC
-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com]
Sent: Sunday, October 28, 2012 4:39 AM
To: General toolset. (wix-users
As this is an e-mail list, attachments get stripped off. You'll need to
post the log in the e-mail itself so it can be seen.
-Original Message-
From: vchauras [mailto:vivekchauras...@gmail.com]
Sent: Tuesday, September 11, 2012 11:02 AM
To: wix-users@lists.sourceforge.net
Subject: Re:
Steven,
It sounds like you are calling one MSI from another. This is not a
Windows Installer recommended practice.
If you need to install two MSI's for your application, you should
consider using a bootloader such as Burn to install them one at a time.
Hope that helps
Chris
-Original
or is there a
better way?
Any suggestions gratefully received.
Thanks
Chris Lord
Product Engineer
Attero Tech, LLC
1315 Directors Row, Suite 107
Fort Wayne, IN 46808
Ph: 260-496-9668 ext. 377, Fax 260-496-9879
email: chris.l...@atterotech.com
Confidentiality Notice: This message
with the only option to repair or remove. Was there a reason
for trying to stop the user installing the update again?
Chris Lord
Attero Tech, LLC
1315 Directors Row, Suite 107
Fort Wayne, IN 46808
Ph: 260-496-9668 ext. 377, Fax 260-496-9879
email: chris.l...@atterotech.com
Confidentiality Notice
heat to extract the COM
registration information.
Chris Lord
Attero Tech, LLC
1315 Directors Row, Suite 107
Fort Wayne, IN 46808
Ph: 260-496-9668 ext. 377, Fax 260-496-9879
email: chris.l...@atterotech.com
Confidentiality Notice: This message is intended solely for the use of
the addressees shown
Christopher
I can partially answer your questions from this side of the pond.
I am originally from the UK and I am quite surprised anyone would want a
specific UK localized installer. I cant remember ever seeing a
specific UK version of any software that I've installed as the US
version
Robert,
You've only posted what the back buton does for the VerifyReadDlg.
What do you have for the Remove button?
Chris
-Original Message-
From: Robert Hermann [mailto:rob.herm...@nicewareintl.com]
Sent: Tuesday, December 06, 2011 3:43 PM
To: wix-users@lists.sourceforge.net
Subject:
Message-
From: Chris Lord [mailto:chris.l...@atterotech.com]
Sent: Tuesday, December 06, 2011 3:19 PM
To: wix-users
Subject: Re: [WiX-users] Wix Uninstall - MaintenanceTypeDlg,
VerifyReadyDlg Dialog sequence is Shown Twice
Robert,
You've only posted what the back buton does
Joe,
My setup has INSTALLDIR property inside the UI section itself rather
than on own, like this
UI
...
Property Id=WIXUI_INSTALLDIR Value=INSTALLDIR /
...
\UI
And this works fine for me. Can't hurt to try it.
Chris
On 08/04/2011 10:57 AM, Joe
directly to the UI
element, not as a child of the UIRef element?
Thanks
_
Joe Tilley
FW Murphy
Software Engineer
Office
(918) 317-4130
Email
jtil...@fwmurphy.com
-Original Message-
From: Chris Lord [mailto:chris.l...@atterotech.com]
Sent
Christoph,
This should answer your question.
http://msdn.microsoft.com/en-us/library/aa368010%28v=VS.85%29.aspx
Chris
On 05/06/2011 09:56 AM, Christoph Goetz wrote:
Hello,
i want to run a second msi ( dotnet 4.0 ) while my setup is runnig.
Is there a way to run this?
Christoph
be installed
that way or does indeed the page need updating in some way?
Chris
On 05/06/2011 08:23 AM, Sam Morris wrote:
On Wed, May 04, 2011 at 12:58:09PM -0400, Chris Lord wrote:
Chaining installers is a general no-no and Microsoft recommend you don't
do it. Second, trying to install software
Sam,
Chaining installers is a general no-no and Microsoft recommend you don't
do it. Second, trying to install software in the Cost Finalise stage is
also not a good idea. Installing something using a custom action makes
it very difficult to roll back should the installation fail or be
Sam,
Chaining installers is a general no-no and Microsoft recommend you don't
do it. Second, trying to install software in the Cost Finalise stage is
also not a good idea. Installing something using a custom action makes
it very difficult to roll back should the installation fail or be
Orlando,
I don't see the screen (you can;t attach screen shots to forum posts
sdaly hence why it may not show up) so I don;t know what error you are
seeing.
However, if you are suggesting that you run one installer from another,
then Microsoft advise strongly against it. If you need to run
Tyler,
Problem 1 - In order for a major upgrade to work, you have to call
RemoveExistingProducts to remove older versions. Given your post, I
don't see that in your execute sequence.
Problem 2 - I can't offer any advice for that, sorry.
Chris
On 04/14/2011 12:35 PM, Tyler Walters wrote:
Miaohsi
Calling one installer from within another is a big no, no and Microsoft
recommends you do not do it. You should use a bootstrapper such as Burn
in order to call which installer you need.
As for exiting gracefully, I think more details on what the installer is
doing would be needed to
with the newer version.
Kevin Burton
Senior Software Engineer
BUYSEASONS
262-901-2000 Office
262-901-2312 Fax
kev...@buyseasons.com
-Original Message-
From: Chris Lord [mailto:chris.l...@atterotech.com]
Sent: Friday, February 25, 2011 11:21 AM
To: General discussion
Kevin,
Lesson 4 is/was based on Wix V3. Rob's reply refers to an addition to
Wix3.5 though I would expect lesson 4 code probably still applies in
V3.5. Depending on which version of WiX you use will determine what
options you have for writing upgrades.
Now, the key is where you place the
in learning how this is done with the
newer version.
Kevin Burton
Senior Software Engineer
BUYSEASONS
262-901-2000 Office
262-901-2312 Fax
kev...@buyseasons.com
-Original Message-
From: Chris Lord [mailto:chris.l...@atterotech.com]
Sent: Friday, February 25, 2011 11:21 AM
To: General
John
Apologies from stating the obvious but why not just remove the option to
run after install altogether.
That way, it does not matter if a reboot is required or not.
Chris
On 01/25/2011 02:43 PM, John Lalande wrote:
Is there some way to run my custom action in the UI sequence just
before
Kevin
What version of windows installer are you targeting. Looks like this
parameter is only available in Windows Installer 4 and onwards.
http://msdn.microsoft.com/en-us/library/aa368276%28v=vs.85%29.aspx
Chris
On 01/25/2011 03:34 PM, Kevin Burton wrote:
I am trying to reference
Kevin
The reason for it being there is stated in the text of the example you
originally posted a link to.
There is also a link off that page to here :
http://wix.sourceforge.net/manual-wix3/create_start_menu_shortcut.htm
See the text in step 2
Chris
On 01/25/2011 03:31 PM, Kevin Burton
Kevin
All you need to know about ICE and more
http://msdn.microsoft.com/en-us/library/aa369554%28v=VS.85%29.aspx
Chris
On 01/25/2011 04:11 PM, Kevin Burton wrote:
I think I figured it out. I was confused since this link was about adding a
shortcut I thought that the registry value had
kev...@buyseasons.com
-Original Message-
From: Chris Lord [mailto:chris.l...@atterotech.com]
Sent: Tuesday, January 25, 2011 2:50 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Where is DesktopFolder?
Kevin
What version of windows installer
Vasu,
If the additional application has its own installer then you have no
option except to use a bootstrapper as you can't start one installer
from within another (called chaining).
Can't help with the second part I am afraid.
Chris
On 11/04/2010 11:46 AM, Vasu Chakkera wrote:
Dear All,
I
Not done this myself but I note there's a section on it in Nicks WiX
book (available from PacktPub.com) which I got last week and just
starting to read :)
On 10/29/2010 03:40 PM, Tom Crozier wrote:
I have searched the web and have tried playing around with adding billboards
to my installer
Alex,
If you want to do upgrades then you have to use an upgrade code and the
upgrade code must remain the same throughout all your versions.
FindRelatedProducts searches for the upgrade code. If it find one that
matches it knows it's found a related product.
Chris
On 10/14/2010 07:21
John,
Just to elaborate, you cannot install a package where the product ID
matches that of an already installed product. You should change either
your product ID to * (which will create a new ID every time you build
your MSI) or alternately, change it manually yourself.
I tend to do the
John,
I don't believe you can do it as an upgrade i.e. all in one go. An
installer is either per-user or per-machine. You can't upgrade a
per-machine install to per-user install or vice-versa.
I think your only option is to un-install your previous version and then
install the new one as
I think you may have sequenced RemoveExistingProducts in the wrong place in
V2.0.0.0.
It either needs to be
InstallExecuteSequence
RemoveExistingProducts After=InstallValidate /
/InstallExecuteSequence
or
InstallExecuteSequence
RemoveExistingProducts After=InstallFinalize /
Richard
Here's some help on doing upgrades
http://blogs.technet.com/b/alexshev/archive/2008/02/15/from-msi-to-wix-part-8-major-upgrade.aspx
Looking at your code, I think you may have sequenced
RemoveExistingProducts in the wrong place.
It either needs to be
InstallExecuteSequence
Thanks Blair.
On 08/20/2010 03:54 PM, Blair wrote:
If the new version of the file has the same name as the old file and goes
into the same directory, keep the component's guid the same.
-Original Message-
From: Chris Lord [mailto:chris.l...@atterotech.com]
Sent: Thursday, August 19
Hi All,
This should be dead quick. Despite reading through numerous pieces of
information, both on MSDN and in the archives, I am still a little
confused by the Component Rules and I'd like to get some clarification
if someone has a moment.
I have an installer that installer an .EXE and a
Did you already have a UIRef in your wxs before you added the
FeatureTree UIRef?
On 08/11/2010 03:00 PM, little.forest wrote:
We'll need to add a new component. And we'd like the end user to choose to
install it or not.
I found the FeatureTree maybe a fit for us. So I add these code:
UIRef
I suspect your original UI refs contain a welcome dialog. The
FeatureTree UI is a complete UI. Its not just a FeatureTree dialog so
the combination of your UIrefs and FeatureTree means you have duplicate
dialogs, hence the error.
If the standard feature tree UI sequence work for you as is,
Sadly, you are getting to the extent of my knowledge and experience here
so I am not sure I can offer much more advice.
What you need is to take your customized version of WixUI_InstallDir and
add to it the useful dialogs from WixUI_FeatureTree. Unfortunately, how
best to achieve that I do
Having said that, I note the name attribute is the same for all the
files. You might want to check if that is acceptable.
On 08/10/2010 06:25 PM, Chris Lord wrote:
Run the uninstaller from the command line and get a verbose log. That
should tell you the reason.
On 08/10/2010 05:48 PM
Michael,
With only one file in the component, you probably don't need the
KeyPath. My WXS doesn't need the KeyPath for a file (I have a single
file in each component) and it passes all ICE tests.
As far as putting files into a specific user folder that should be OK if
you are doing a
With all due respect, I think you've missed what Pally was telling you.
2010.2.0.0 is an invalid version number for a product version. The
first number (Microsoft calls that the major version number) must be
less than 255. Since yours is 2010, its invalid and you can't use it.
This is also
Short answer.no.
But if you just need a single installer, look into using a bootstrapper
which can run either your 32-bit or your 64-bit MSI depending on the
environment it's being installed into.
On 07/07/2010 09:07 AM, Sanjay Rao wrote:
Can we use a single MSI installer on both
Jeff,
What does the verbose log say?
Chris
On 05/25/2010 02:55 AM, s...@pacaccess.com wrote:
Prior to my upcoming release I used a VisualStudio deployment project to
create the installer. For my upcoming release I've built an installer
using Wix. Everything seems to be working with the
Jeff,
Several people including myself have reported seeing this during the
course of an installation. It appears to only happen once in a while so
its very difficult to catch. In fact, I had it happen yesterday when I
was trying to install either WiX or WixEdit (I don't remember which)
onto a
I believe this is what you are suggesting.
http://msdn.microsoft.com/en-us/library/aa368010%28VS.85%29.aspx
As the document says, this is a deprecated feature and should not be
used.
Instead, you need to use a bootstrapper to call the required installers
one at a time.
-Original
BTW, we still need to talk to the Larocko's about this weekend...That is
as long as you can and still want to go.
-Original Message-
From: Alex Cater [mailto:alex.ca...@apdcomms.com]
Sent: Monday, October 19, 2009 06:03
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] How
How weirdI send a message to my wife and it appears via
WiX..apologies everyone!
-Original Message-
From: Chris Lord
Sent: Monday, October 19, 2009 12:19
To: wix-users
Subject: Re: [WiX-users] How to populate a list box in a msi dialog
duringruntime
BTW, we still need to talk
Pally,
I, like Alex, have seen the same thing and recently too. As I recall, I
waited several minutes for an installer to think before I got bored
and cancelled it. I just put it down to Windows being awkward as when
I restarted the installer, the thinking time was either non-existent or
. So there is a
problem.
-Original Message-
From: Chris Lord [mailto:chris.l...@atterotech.com]
Sent: Wednesday, September 16, 2009 10:46
To: wix-users
Subject: Re: [WiX-users] (no subject)
Pally,
I, like Alex, have seen the same thing and recently too. As I recall, I
waited several
The source has no affect on the location the file is placed when it is
installed on the target machine. That is set by the directory structure
you have defined with the directory components.
The source should point to the file location of CID_Demo.pdf on your
machine that is to be included in
with MSI caching?
Thanks,
Tom
Chris Lord wrote:
Tom
For files your installer places on the hard disk, the uninstall should
remove them automatically unless they are still in use. There should
be no need for you to manually remove these files. Directories are a
different matter
Tom
For files your installer places on the hard disk, the uninstall should
remove them automatically unless they are still in use. There should be
no need for you to manually remove these files. Directories are a
different matter as the uninstall will not remove it if the directory is
not
No. You cannot Chain one MSI from another. This is a limitation of
the Windows Installer technology.
To run both MSI's you'll need a bootstrapper. Have a search through the
archives as there are plenty of references of bootstrappers as this is a
fairly frequent question.
Chris
I run it...plain and simple. I have a dedicated machine with removable
drives that I can image to a base setup of Win2000, Win XP, Vista and a
Win 7 install will be added in the near future.
From there, I can test a clean install, or I can install a previous
version and make sure it gets
Take at look at the WiX tutorial at
http://www.tramontana.co.hu/wix/lesson4.php
This has some detail on doing upgrades. That should start you on your
way.
Chris
-Original Message-
From: John D. Marinuzzi [mailto:nu...@hypack.com]
Sent: Wednesday, July 22, 2009 13:12
To:
Calling of one install from another is called chaining. It's not that
WiX doesnt support chainingNot being able to Chain installs is a
limitation imposed by Windows Installer technology which WiX uses. So
any MSI you build has this limitation whether it's built using WiX or
otherwise.
Akash,
Typical and Complete are names of feature sets. A feature set
installs a particular group of components. Each feature set can install
a different set of components (though a component can be used in more
than one feature set if needed). An install always requires at least
one
Tom,
If your current installer generates an .MSI file to install your product
then WiX contains a tool called Dark that can convert an Msi into a
Wxs file for you. I haven't used it a lot but worked when I swapped
from Installshield to WiX to get me going.
Chris
-Original Message-
My application uses a .NET object that requires the use of TFTP.
Unfortunately, on a Vista install, the software doesn't work correctly
because the Vista firewall blocks it. A simple exception for the
application fixes this. However, rather than get the user to do this
manually, I'd like my
Apologies everyone. A quick search this morning and I find Bob's blog
with all the information I need! Have no idea how I missed that. Must
have been tired.
-Original Message-
From: Chris Lord
Sent: Tuesday, May 05, 2009 10:44
To: wix-users
Subject: [WiX-users] Setting
Afraid not. It's not a WiX issue but rather a Windows Installer
limitation.
If you need to run two MSI's, your only option is to use a bootstrapper
to call the MSI's separately.
Chris Lord
-Original Message-
From: dedek mrazko [mailto:aleask...@gmail.com]
Sent: Wednesday, February
the
above settings from said shortcut when it's no longer needed.
Any help is gratefully received
Thanks
Chris Lord
--
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest
a CustomAction to set that. The native
Windows Installer ability doesn't have functionality to do that.
-Original Message-
From: Chris Lord [mailto:chris.l...@atterotech.com]
Sent: Friday, February 13, 2009 07:47
To: wix-users
Subject: [WiX-users] Setting XP compatible mode on Vista Shortcut
Hello
? If so, what do I have to set in order
to change that so that I correctly detect the Installshield and thus can
remove it?
Thanks
Chris Lord
--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants
Thanks Richard, I kind of guessed that was the case.
I have two further questions
1) Would it be possible to set ALLUSERS and then detect the previous
products and if found, give a warning and exit the installer. If a
previous product isn't found then clear all users and continue with the
-
From: Richard [mailto:legal...@xmission.com]
Sent: Friday, January 23, 2009 12:24
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Removing a previous Installshield installation
In article h2e30106ea2f.1232730730.scalix.atterotech@mhs,
Chris Lord
I have application that requires the installation of some 3rd party COM
objects. I have used Heat to harvest the details from all the necessary
files and after a lot of fiddling, I have managed to get the files to
install and I have verified they are copied onto the HD of the target
machine in
Arnson [mailto:b...@joyofsetup.com]
Sent: Monday, December 22, 2008 16:18
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Incorporating Heat output into a project
Chris Lord wrote:
One thing I did do was to compare the MSI files of a working
installation created
that an upgrade requires
uninstallation of the original software but there are settings set up by
the user in the registry which would also be removed. I'd like to save
the user from the hassle of having to setup things up again. Is this
possible and if so how?
Thanks
Chris Lord
Attero Tech LLC
Hello,
Want to look up some things in the Wixwiki but all I get is blank pages.
The search works but any page I select shows no information. Is it me
or is there a problem?
Thanks
Chris
-
This SF.Net email is sponsored
This is what I have used for my application.
Shortcut Id=StartMenuShortcut Name=My Application Description=My
Application Shorcut WorkingDirectory=INSTALLDIR
Target=[INSTALLDIR]MyApplication.exe /
The MyApplication.exe needs to be the exact filename of the executable
that the shortcut is
uninstall it, unregister it. While I can write the install/uninstall
part of the installation easily enough, how do I go about registering
and unregistering the DLL.
Thanks
Chris Lord
-
This SF.Net email is sponsored
. Registered in Scotland No.
SC151456
Registered Office - Helix Building, West Of Scotland Science Park,
Glasgow G20 0SP
Email Disclaimer
-Original Message-
From: Chris Lord [mailto:[EMAIL PROTECTED]
Sent: 23 October 2008 16:26
To: wix-users
Subject: [WiX-users] Register a DLL
Hello,
I
there is an easy way to do what I need. What am I missing?
Thanks
Chris Lord
Product Engineer
Attero Tech, LLC
-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based
once my installation is complete.
Thanks in advance
Chris Lord
Product Engineer
Attero Tech, LLC
1315 Director's Row, Suite 107
Fort Wayne, IN 46808
-
This SF.Net email is sponsored by the Moblin Your Move Developer's
, that would be your CA Id.
On Fri, Oct 17, 2008 at 10:35 AM, Chris Lord
[EMAIL PROTECTED]wrote:
Hello
I need some assistance in completing my first installation.
1) Using the inbuilt UI adds rather too many forms for my needs is
there any way to cut them back and not show some of them?
2
=yes TabSkip=no
Text SourceFile=!(wix.WixUILicenseRtf=$(var.licenseRtf)) /
/Control
Good luck!
2008/10/17 Chris Lord [EMAIL PROTECTED]
Thanks Chad, further information
1) I found some information in the help but I can't locate the names
of all the dialogs. It mentions about
85 matches
Mail list logo
