All advertised entries (CLSID, ProgId, Shortcuts) are implemented via a
mechanism that places an encoded version of the ProductCode, ComponentCode,
and FeatureId into the entry-point. A health check is made of the
indicated feature, and after it runs (possibly repairing, if needed) the
keypath of
Read the descriptions of the following ICEs: ICE18, ICE38, ICE43, ICE57*,
ICE64, ICE91. (I'm sure I'm missing one or more additional pertinent ones
somewhere)
*ICE57 doesn't check the value of ALLUSERS because that property can be
overridden during an installation, so if it thinks the referenced
Hi Rob,
Thanks a lot! I set Secure=yes to that property. And the condition for CA
works. So my problem is resolved.
Regards,
Chunyan
-Ursprüngliche Nachricht-
Von: Rob Mensching [mailto:r...@robmensching.com]
Gesendet: Freitag, 30. Oktober 2009 17:00
An: General discussion for
Hi all,
I'm using populating a ListView so I can display a prerequisite screen
at the very beginning of the installation.
I'm using the following code to embed the relevant bitmaps...
Binary Id=WiXTickIcon SourceFile=..\Common\graphics\tick.bmp /
Binary Id=WiXCrossIcon
Ok after further investigation it seems someone on our team had renamed
a *.ico file to *.bmp and when I referred to that bmp it worked and when
I tried actual bmp files it did not work. So if anyone else stumbles
across this, the ListItem Icon must, in fact, be an actual *.ico file,
and it looks
My application is installed at an enterprise level where there are separate SQL
servers, SSRS servers and IIS servers and even if you have admin privileges on
one box you may (and probably won't) on another box. I understand that this is
not a typical installer.
I ended up just showing a hidden
Blair, could you elaborate on how writing shortcuts into unloaded profiles
breaks things?
Thanks
-Original Message-
From: Blair [mailto:os...@live.com]
Sent: Thursday, October 29, 2009 6:58 PM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] SendTo
Try using mszip instead of high for compression on your media tag
see if that changes the size of the cab file.
Essentially though you're comparing apples and steaks (see
http://en.wikipedia.org/wiki/List_of_archive_formats). If you want your
files be installed without any extra work you're going
Hi
How to change the installation to point to C drive, rather than to programfiles
or any other directory
Directory Id=TARGETDIR Name=SourceDir
Directory Id=ProgramFilesFolder
Is there any easy way to do it.
Regards
Anweshi
I'm having trouble getting a VBScript custom action to work. It's
purpose it so backup some files that the major upgrade may otherwise
delete.
My WiX source looks like this:
Binary Id='project_backup.vbs' SourceFile='project_backup.vbs'/
CustomAction Id='setProjectFolder'
Hi wix-users,
I tried to compile the sampleListbox from Wix Tutorial 10.1. I
downloaded the source code and tried to build the dll. However, I got
the error:
1dutil.lib(precomp.obj) : fatal error LNK1103: debugging information
corrupt; recompile module
I updated my wix install to the latest
What version of the C++ compiler are you using?
On Mon, Nov 2, 2009 at 7:20 AM, Jiang, Chunyan (GE Healthcare)
chunyan.ji...@ge.com wrote:
Hi wix-users,
I tried to compile the sampleListbox from Wix Tutorial 10.1. I
downloaded the source code and tried to build the dll. However, I got
the
*sigh* Sorry for this... being a WiX dummy, I'm having difficulty
finding this in the docs. Could I ask for a pointer to what's probably
right in front of my face?
(For me, the COM exe is static; the interface won't be changing.
Nevertheless the idea of a minimal XML is appealing.)
On
On Mon, Nov 2, 2009 at 3:30 PM, Pally Sandher pally.sand...@iesve.com wrote:
Try using mszip instead of high for compression on your media tag
see if that changes the size of the cab file.
It does. It becomes 99MB, i.e. bigger.
If you want your
files be installed without any extra work
On Mon, 2 Nov 2009 07:52:10 -0800, Rob Mensching wrote:
Rob,
What version of the C++ compiler are you using?
Besides, *which* compiler? There are quite a few of them...
Bye,
Gábor
---
DEÁK JAHN, Gábor -- Budapest, Hungary
Bob Arnson wrote:
Smith, Stan wrote:
I'm trying to find someone who can supply information about the
WIX 3.0 binary distribution file 'difxapp_ia64.wixlib' as it is not
present in the WIX 3.0 binary distribution and documented to be
included?
It should be. Please open a bug on
What's special about the C: drive? Maybe you need the ROOTDRIVE or
WindowsVolume property.
Phil Wilson
-Original Message-
From: Anu Dev [mailto:queryl...@yahoo.com]
Sent: Monday, November 02, 2009 6:49 AM
To: WIX
Subject: [WiX-users] How to change the installation to point to C:\
Hi
I'm new to WiX and have an installer that installs a set of PCI drivers.
An existing service uses these drivers and I need to stop it before
upgrading drivers, then restart it after the drivers have been installed
such that the service uses the new drivers. The service has a seperate
Hi All,
I'm trying to write some conditional feature code, based on whether a
certain file is available on the installation media. I've been setting a
property like this:
Property Id=Feature1
DirectorySearch Id=Feature1 Path=[SourceDir]
FileSearch Id=Feature1
The WScript.Echo won't work - that's supplied by the WSH object, not by MSI. Do
you see that message?
MsiProvideComponent is normal - any of the entrypoints that have a Darwin
descriptor (COM,file associations, shortcuts) use that to locate the target
file (causing repair if needed).
Apart
The way you worded your question it appeared that you were asking if you
could simply compress a .cab using 7-zip's LZMA compression algorithm
I may be too used to people on this list expecting the minimum amount of
effort to solve anything remotely difficult (and subsequently blaming a
lack of
Blair,
thank you very much for your detailed explanation. Now I understand what the
problem is. :-)
I just filed a proposal
https://sourceforge.net/tracker/?func=detailaid=2890852group_id=105970ati
d=642717 to add your explanation to the WiX documentation.
Thanks
Markus
-Original
What you are looking for is the Class, ProgId and Interface
elements.
Neil
-Original Message-
From: IFM Lists [mailto:jkli...@ifm-services.com]
Sent: 02 November 2009 16:05
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Heat and .exe COM objects
One more note - IIRC MSI's advertised shortcuts aren't drop targets and don't
show up in the SendTo context menu even when they're in the SendTo folder.
You'll need a non advertised shortcut.
Phil Wilson
-Original Message-
From: Evan Beeton [mailto:ebee...@informasoftware.com]
I know DTF has some support for external UI, but once you have your own forms,
and you've called (Msi)SetExternalUI(Record), why not just call
MsiInstallProduct with the command line properties you want to set?
Phil Wilson
-Original Message-
From: Rob Mensching
I'd like to add that SelfReg was a 1980s and early 1990s concept. By the end
of the 1990s it was recognized as being a prime contributor to the DLL
Hell problem that as killing redistributables (anyone remember how messed
up the VB runtime could get?).
Anyway, the Windows Installer documentation
Blair,
in a different context you wrote:
It is best to make your installations pure-perMachine or pure-
perUser
and never mix them
There is one thing I do not understand in that context: I always had the
impression that it is up to the *administrator* to decide whether to install
a software
Thanks, I found that and fixed a few other VBScript problems and now I
have it working. (Only to discover other problems, however.)
Scott
On Mon, Nov 2, 2009 at 1:15 PM, Wilson, Phil phil.wil...@wonderware.com wrote:
The WScript.Echo won't work - that's supplied by the WSH object, not by MSI.
I am a beginner to MSI and WiX and have a question on the InstallerVersion
attribute:
How to know what version of WindowsInstaller my .msi will need to run
correctly?
Is there some kind of table that I did not discover so far, containing all
WiX / MSI features plus the needed version
If I understand correctly, there are two ways to modularize my setup:
Fragments and Merge Modules. So the question is: Which one to use?
For me it looks like Merge Modules being a more heavy weight solution, but
the benefit is that those are a product-independent standard (i. e.
InstallShield
I will name boxes X Y, and consider users A B.
User A logs into box X, then logs out and logs into box Y, where they make
several changes in their profile.
User B logs into box X, then installs an application that changes user A's
profile.
Later when user A logs into box X, the profiles are
You should be able to use the ServiceControl table (which you can author
using the ServiceControl element in WiX).
-Original Message-
From: shane_cor...@selinc.com [mailto:shane_cor...@selinc.com]
Sent: Monday, November 02, 2009 9:48 AM
To: wix-users@lists.sourceforge.net
Subject:
Thanks for the edification.
-Original Message-
From: Blair [mailto:os...@live.com]
Sent: Monday, November 02, 2009 3:12 PM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] SendTo shortcut for default and alluser profileson
multiple OS's - Email found
All resources (files, registry entries, etc.) can generally be divided into
three spaces: those that live in administrator per-machine areas (C:\Program
Files, etc.), those that live in the user profile, and those very few that
live in shared document regions.
If your installation requires access
On Mon, Nov 2, 2009 at 7:14 PM, Pally Sandher pally.sand...@iesve.com wrote:
Could be worth feature requesting for something like Burn but taking
modern internet connections into consideration I don't see many people
being that bothered about it if they have to put that amount of effort
in to
More-or-less yes, you have it right.
There are several servicing issues related to Merge Modules, and some of
those issues are carried into the way that WiX incorporates Merge Modules
(making them even harder to deal with than they already would have been,
especially as relates to patching/patch
If you don't specify, WiX currently defaults to 1.0 (100).
Very brief matrix:
MSI 1.x - basic MSI support, 32-bit only.
MSI 2.x - added 64-bit support.
MSI 3.0 - improved patching.
MSI 3.1 - improved external ui.
MSI 4.0 - Vista/2008 only. Incorporates
Did you try a clean build? i.e. Delete your build output directory and build
again.
Thanks,
Mike Carlson
-Original Message-
From: Jiang, Chunyan (GE Healthcare) [mailto:chunyan.ji...@ge.com]
Sent: Monday, November 02, 2009 7:20 AM
To: General discussion for Windows Installer XML
Are you building 32-bit, or some flavor of 64-bit?
-Original Message-
From: Mike Carlson (DEV DIV) [mailto:mica...@microsoft.com]
Sent: Monday, November 02, 2009 1:52 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Link error for dutil.lib
Did you
I don't understand how ResolveSource (which looks for your installation MSI)
applies to your situation. (ResolveSource in effect is a no-op in initial
installations, since the source was supplied to begin with, and is used to
ensure access to the non-stripped MSI during maintenance installations
I tried using the ServiceControl table but it looks like it's used to
specify that you would like service to start/stop when the the installer
begins an install/uninstall. That's not what I'm trying to do. I want to
sequentially stop a service, run my installer to completion, then start
the
If you select both for Stop and for Start, it will stop the service before
changing any of your files/registry/etc. during both installation and
removal and start it again after making those changes. Isn't that what you
are describing you want to do?
-Original Message-
From:
In article 162de7480911020831o4b123747xc933d27b4fbf8...@mail.gmail.com,
Wesley W. Terpstra wes...@terpstra.ca writes:
[...] For such a big
savings in download-time I think that's a reasonable trade-off.
Have you been receiving complaints about download times?
Doing the simplest thing
In article
d91a1dd8a8f2ba459644b8f3b7e517ddac0ee4e...@exvmbx015-4.exch015.msoutlookonline.net,
Tom Crozier tcroz...@rackwise.com writes:
My application is installed at an enterprise level where there are
separate S QL servers, SSRS servers and IIS servers and even if you have
admin
That seems to work fine for installation, but can I force the service to
stop on uninstall?
Thanks again!
--
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to
Works the same way. That is why you say both instead of install.
The stop happens before any files are erased or registry keys/values are
removed, or any other related activities.
-Original Message-
From: shane_cor...@selinc.com [mailto:shane_cor...@selinc.com]
Sent: Monday, November
Perhaps I'm misunderstanding. On install I'd like to stop the service, do
the installation and then start the service. On uninstall I'd like to
stop the service, and uninstall without starting the service back up at
the end of uninstallation.
On Mon, Nov 2, 2009 at 11:41 PM, Richard legal...@xmission.com wrote:
In article 162de7480911020831o4b123747xc933d27b4fbf8...@mail.gmail.com,
Wesley W. Terpstra wes...@terpstra.ca writes:
[...] For such a big
savings in download-time I think that's a reasonable trade-off.
Have you been
I thought the service used the drivers, but existed before the drivers were
installed (which would suggest that they would be started again upon
uninstallation of the drivers).
Change Start to install, leave Stop as both.
-Original Message-
From: shane_cor...@selinc.com
Uh, according to this link:
http://msdn.microsoft.com/da-dk/library/dd408041%28en-us,VS.85%29.aspx
Is MSI 4.5 also available on Windows XP SP2 as a redistributable:
Windows Installer 4.5 is available as a redistributable for Windows
Server 2008, Windows Vista with Service Pack 1 (SP1), Windows
Quoting myself: MSI 4.5 - ..., and a redistributable ... for supported
pre-Vista platforms.
-Original Message-
From: Thomas Due [mailto:thomas@scanvaegt.dk]
Sent: Monday, November 02, 2009 11:09 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users]
IIRC, they ship 4.5 as part of XP SP3 and Vista SP1, along with the
equivalent service packs for the corresponding server OSs.
-Original Message-
From: Blair [mailto:os...@live.com]
Sent: Monday, November 02, 2009 11:31 PM
To: 'General discussion for Windows Installer XML toolset.'
52 matches
Mail list logo
