Oh, I am sorry to hear that.
In one of my msi installers, I need to modify some files after
installation. Then I chose to write a custom action that call a .exe file to do
this for me. Of course this should be done after install operation, and it need
to know where the files locate on.
Make a directory with an Id of PERSONALFOLDER. Make a directory under that
directory that is named "Foo". Install into that child directory.
Make a secure property with an Id of PERSONALFOLDER (must be spelled exactly
the same) and inside the content of the Property element perform your
registry s
Can you describe your build system?
-Original Message-
From: HuangRunzhen [mailto:h_runz...@hotmail.com]
Sent: Thursday, November 12, 2009 9:12 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] How to read a file to a property
Thanks. Do you know where I can find a tutoria
Hello,
My Bing/Google skills are failing me and I know I'm missing something obvious.
What I'd like to do is have an install that defaults to PersonalFolder\Foo, but
if the results of a registry search turns up a different directory, my install
uses \Foo as the installation directory instead.
Thanks. Do you know where I can find a tutorial or example about this?
Runzhen
> From: os...@live.com
> To: wix-users@lists.sourceforge.net
> Date: Thu, 12 Nov 2009 20:15:46 -0800
> Subject: Re: [WiX-users] How to read a file to a property
>
> When you build, you have access to the file you
You need both 32-bit and 64-bit registry components. However, 32-bit code
normally can't access 64-bit registry areas, so the "correct" solution is a
separate package for each bit-ness.
-Original Message-
From: phillip_sid...@dellteam.com [mailto:phillip_sid...@dellteam.com]
Sent: Thursda
WiX allows the use of either the COM tables or the Registry table and
exposes both easily enough, but the default preference in the toolset is for
the Registry tables.
-Original Message-
From: Christopher Painter [mailto:chr...@deploymentengineering.com]
Sent: Thursday, November 12, 2009
WiX can scale to virtually anything that Windows Installer/MSI can support,
including all of its extension points, and the entire functionality of the
platform is exposed by the toolset. Understanding how to use it requires
some understanding of Windows Installer, so be prepared to spend some time
What is the REINSTALLMODE value when you apply the patch? What does the
selection manager say in the verbose debug log from the patch application?
-Original Message-
From: Grebil, Bryce [mailto:bryce.gre...@wolterskluwer.com]
Sent: Thursday, November 12, 2009 9:50 AM
To: General discussio
You have different MSIs for the different languages. Any chance you could
release different MSPs (one for each language) in the same fashion?
The only further insight I could give would probably require digging into
your actual MSIs.
-Original Message-
From: Shawn Dwyer [mailto:shawn.o.dw
When you build, you have access to the file you will be adding to the MSI
for installation. That file must exist at least before you call light.exe
when it gets bound, but depending on your build environment it will likely
be ready before you even call candle.exe. What I suggest is to read that
fil
This was code we added on especially for IE. There isn't anything in WiX or
Windows Installer to do that natively.
-Original Message-
From: Andreas Mertens [mailto:andre...@nvisionideas.com]
Sent: Thursday, November 12, 2009 5:57 PM
To: 'General discussion for Windows Installer XML toolse
I don't know where you draw the line between 'simple' and 'top shelf', a few of
the products whose installers were developed entirely with WiX are:
Microsoft Office Enterprise 2007 (over 4,600 files and 53,000 registry keys)
Microsoft Visual Studio 2008
Sun Microsystems MySQL
> -Original Me
Perfect, I have not seen this site!
Thank you!
-Original Message-
From: salever.lee [mailto:salever@gmail.com]
Sent: Thursday, November 12, 2009 7:59 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] setup.ini... (Wix 3.5)
Hi,
As I known, Wix ha
Hi,
As I known, Wix has some elements to deal with ini files. See more in Wix
toturial. There are some examples which include ini file operations.
More At http://www.tramontana.co.hu/wix/lesson1.php#1.5
Good luck.
2009-11-13
salever.lee
发件人： John H. Bergman (XPedient Technologies)
I am not sure what you are saying - is Wix or MSI actually treating BHO
installers as a special case and kill all related IE instances? Do I need
to do something special to identify my code as a BHO in order for this to
happen, because right now it isn't happening...
Andreas
-Original Messag
Hi,
You can try to use *.ini files instead of *.txt files. As I known, Wix has
its way to deal with ini files, See Wix tutorial.
Good luck.
2009-11-13
salever.lee
发件人： HuangRunzhen
发送时间： 2009-11-13 05:16:57
收件人： wix-users@lists.sourceforge.net
抄送：
主题： Re: [WiX-users] How to re
The problem was having two driver packages installed in the same
directory. The solution was to move component #1 to it's own directory
during installation and everything seems to be much happier.
From: shane_cor...@selinc.com
To: wix-users@lists.sourceforge.net
Date: 11/12/2009 09:5
After a great deal of wrangling with this issue earlier this year, I
concluded that it's easier to get your app to check both locations for
the registry keys ...
Wendell
On Thu, Nov 12, 2009 at 1:00 PM, wrote:
> Ok, so it was writing to the Wow6432Node. So the next question:
>
> How can I force
Ok, so it was writing to the Wow6432Node. So the next question:
How can I force a 32bit installer to install registry keys to both the standard
and Wow6432Nodes?
Thanks.
- Phil
-Original Message-
From: Wendell Joost [mailto:wende...@gmail.com]
Sent: Thursday, November 12, 2009 12:19 P
Thanks.
I do need data from a file I am installing. Could you explain in more detail
"how to read from the file while building and populate your property that way"?
Do you mean I read the file from machine and put into a property and use it in
CA?
If I use a deferred CA, can I change th
The biggest difference between InstallShield and WiX in registration ( assuming
you follow best practices and don't use SelfReg / CA's ) is the use of the
registry tables in WiX versus certain COM tables in InstallShield.
Both tools have the capability to extract COM from dll's and it's a bit o
Blair,
Your answer was what i was looking for. I did not realize (and had not read
anywhere) than you can treat the session object like a key/value object to
get to the session properties.
ie:
string MyString = session["MYPROPERTY"];
session["MYOTHERPROP"] = "SomeValue";
That was what i was look
>From just initially talking about or thinking about WiX my first guess would
>be that this would be the option for simpler installation processes/tasks and
>that the 'Top Shelf' products (with regard to price not quality) would pull
>the heavier weighted install stuff.
I would be interested in
I'm afraid I spoke too soon at 2am last night although they apply to the
Spanish MSI just fine when verifying with Orca, when actually trying to
install against the Spanish version yeilds "No valid sequence could be found
for the set of patches." It works fine against English version of the MS
One of the big issues I've had with InstallShield and other products is
proper registration of files. Most of the time this area was OK, but
there were times when one or two files would not register causing me to
create Custom Actions to do so.
How would this be handled in WiX and is it reliable?
Anything? Really? I'm sorry, I like WiX a lot but I can list out a couple
dozen glaring feature and usability gaps. WiX is nice but let's keep some
perspective here.
--- On Thu, 11/12/09, Brian Simoneau wrote:
> From: Brian Simoneau
> Subject: Re: [WiX-users] InstallShield 2010 vs Instal
I have and am using InstallShield 2009 for our existing product but for new
product I started using Wix and there are some good and bad about each
Installer.
InstallShield - Good : Visual editor, scripting (by the way it is readable)
Bad: Pricy, can't add newer technology
Are you running on x86 or x64? 32 bit installer will be remapped on
x64 OS, If x64, registry entries redirect to Wow6432Node, e.g.
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Communicator
instead of:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Communicator
Wendell
On Thu, Nov 12, 2009 at 9:33
Is there any kind of UI with WiX? I like InstallShield because it takes
care of he nuts and bolts for you yet allows tweaking where needed.
Is WiX scripting based or should you be a heavy duty developer to use
it?
I guess I can download and take a look.
Any further info on this or the IS 2010 V
I looked around and could not find much if any documentation around this
topic... do you know where I could find any type of reference material?
The setup.ini file is in the same directory as setup.exe and the .MSI file.
Is there a way to code the setup.exe via Votive to use the .ini file when/if
I have an MSI that runs under an administrative account, it successfully
updates the registry on Win2K3 and XP, but when I execute the same MSI
on Windows Server 2008, it makes no changes to the registry. Note the
installer log indicates that the install was completely successful!
Is anyone els
Sorry, meant to include the code from the RegistryValue in the initial
post.
The value being written to the registry is just defined in a separate
config file
The base MSI has version 1.5.1.0 defined as the version number, while
I have a PCI device that is a multiport serial adapter. The installation
procedure is to use an INF that uses mf.sys to enumerate X number of
serial ports. Once they have been enumerated I can install my driver
package for each serial port.
Using WiX to create an installer for this scenario,
First step is to describe the location of the INI file in such a way as to
enable using the IniFileSearch element. Easiest may be to have your
bootstapper supply a property to the MSI with the INI file's location.
-Original Message-
From: John H. Bergman (XPedient Technologies)
[mailto:joh
With BHOs we actively looked for running IE instances and either added them
all to the RM session (in the case of Vista+) or offered to the user to kill
them (in the case of XP/2k3).
-Original Message-
From: Andreas Mertens [mailto:andre...@nvisionideas.com]
Sent: Thursday, November 12, 2
Use session Properties. They are populated from the Property table only at
the beginning of each sequence (before your immediate CA runs) and can be
read and written by immediate CAs.
The "[PropertyName]" syntax used in formatted fields of the database (such
as some of the XmlConfig attributes and
I would add WiX to the list of considerations. I have used InstallShield and
Wise in the past. We decided several months ago to either migrate to WiX or
upgrade Wise. We chose WiX and have not looked back.
Unless you use the scripting engine of IS, which I would heavily advise
against, WiX wil
Regarding properties from the UI not retaining their values into the execute
sequence, look into 'SecureCustomProperties', ref:
http://msdn.microsoft.com/en-us/library/aa371571(VS.85).aspx
-Original Message-
From: David Drake (Excell Data Corporation) [mailto:a-ddr...@microsoft.com]
S
Only when you drop your requirement to install multiple versions to
different paths simultaneously.
-Original Message-
From: Jiang, Chunyan (GE Healthcare) [mailto:chunyan.ji...@ge.com]
Sent: Thursday, November 12, 2009 2:40 AM
To: General discussion for Windows Installer XML toolset.
Sub
If the ProductCode is the same (Minor Upgrade), you can't change directories
AND leave the previous installation in an old directory (there is no
side-by-side installation of more than one instance of the same
ProductCode).
If the ProductCode is different (Major Upgrade), you have to either have t
My company was using InstallShield before switching to WiX. I have
never used InstallAware, but the only advice I can give is to use WiX.
It's free and can do anything that the commercial products do, sometimes
better.
-Brian Simoneau
-Original Message-
From: Matt Walker [mailto:matt.wal
I am attempting to pass information in and out of a C# Custom Action, and am
having a hell of a time with it.
The problem I am attempting to solve is this:
There is a system XML configuration file on my target system. The path to the
file is always known. I need to look into this file and dete
Has anyone used Setup.ini to configure the public properties of an install? I
am having some difficulty getting this to work.
I am using a bootstrapper that installs .NET 3.5SP1, and then an MSI that has
public properties deailing with things like Server names, user accounts, etc.
I cannot
Hi All,
I'm new to the group and was pointed here by an individual from whom
I've received valuable assistance on many .NET, install related topics
over the past several years. I know this is a Wix users group, but I'm
hoping someone can give me some insight, guidance, etc.
We as a company
I am having an issue with updating a project, and I am not sure if there is
anything I can do in Wix to fix this.
I have created a Browser Helper Object (BHO), a type of COM object that acts
as an add-on to Internet Explorer V6 or later. I have used Wix to create
its installer and that all works
Dear Pally Sandher:
Thanks very much!
I will try both and I hope they will be useful. My job is making users can
"change" product installation by click "change" button on the maintenance
dialog. And I already have a customd dialog to force users to choose only one
of the features throu
I'm assuming you're trying to use the SelectionTree Control.
Looking at a verbose log using WiXUI_Mondo, when I select & deselect
Features for install in the SelectionTree Control on the CustomizeDlg I
see things like the following:
MSI (c) (3C:E8) [12:24:06:682]: PROPERTY CHANGE: Modifying
MsiSe
Without using an external UI or "embedded" UI I seriously doubt it. The
Windows Installer UI doesn't support changing the modality (and rightly
so in my opinion, the only thing more annoying than apps which stick
dialogs to the top of your screen are apps which automatically switch
focus when they
Look up setup.exe & msistuff.exe in the Windows SDK. It does basically
what you're asking for.
Most bootstrappers will have some support for this. I've never used
setupbld.exe myself but you could do something this simple by wrapping
your MSI in a self-extracting archive using 7zip, WinRAR etc.
Pa
What does the RegistryValue code look like? That might help people tell
you what's going wrong. If the value you're writing in this
RegistryValue is a Property which differs *at run-time* in the 2 MSI's
there may not actually be a problem here, it could be expected
behaviour.
Palbinder Sandher
So
Hi,
Since my requirement is special, which includes both new install and update, I
would like to design my package as this:
* One MSI(installation package) to do the new install
* One MSP (patchwork) to do the update
* One MSM (merge module) to contain the common part of new install and update
Hi all,
I have the following Property defined...
Then during the InstallUISequence, After CostFinalize, I change this
value in VBScript to either
Session.Property("PREREQ_IISMST") = "IIS Management and Script Tools and
IIS 6 Compatibility Installed."
When it's IIS7 Or just...
Session.Property(
Hi Blair,
Thanks a lot for your suggestion.
Here I would like to summarize the workflow:
Bootstraper.exe should do the following steps:
* Do the UI, list all installed path, ask user to select one to upgrade
* When one installation is selected, remove this installation (should not
totally remov
Hi,
Here is a problem:
How to make features work like radio buttons ? If I want user to select only
one of some features.
2009-11-12
salever.lee
--
Let Crystal Reports handle the reporting - Free Crystal Report
Hi,
You can try to deal with strings using C++ program, and with an exe file or
dll file , put it in tag. Is this helpful?
2009-11-12
salever.lee
发件人： Blair
发送时间： 2009-11-12 15:18:51
收件人： 'General discussion for Windows Installer XML toolset.'
抄送：
主题： Re: [WiX-users] How to set
56 matches
Mail list logo
