You can suppress harvesting that using the -sreg argument in heat.exe.
Sample:
> heat dir c:\folder\with\files -out dynamic.wxs -ag -sreg
-ag sets to component guid to "*" to have them autogenerated during compile
time.
Best regards,
Sebastian Brand
Instyler Setup - Creating WiX-based MSI insta
Blair,
I have tried the HEAT.EXE, but it is giving me the error "Could not harvest
data from a file that was ecpected to be a assembly"
I have some assemblies in the folder structure, which needs to be copied on
user machine.
Please suggest for the solution
Thanks
Jaspreet
__
NOT Installed, not NOTInstalled. There should be a space there (they are two
different words).
-Original Message-
From: Prabhakaran Paulraj [mailto:prabhakaran_paul...@dynamicbi.com]
Sent: Tuesday, August 25, 2009 3:59 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] How to
Would some incantation of HEAT.EXE work?
-Original Message-
From: Jaspreet Nabha [mailto:jaspreet.na...@headstrong.com]
Sent: Tuesday, August 25, 2009 4:02 AM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Copy folder structure
Hi All,
I am using WiX3.0 a
Wrap the s with for the "common" ones AND the
ones that vary based solely on the name of the environment?
Note: this is a quick-and-dirty example. I haven't compiled it, but is
should basically be what you are looking for.
-Original Message-
From: Maillet, Ed [mailto:
And correspondingly:
-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com]
Sent: Tuesday, August 25, 2009 1:19 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] How to start an executable without showing
commandline
Normally it is considered Best Practice to keep the UpgradeCode the same for
the entire life of a product (you don't change it between versions). This
makes it easier to prevent reinstalling 2.x when 3.x is already installed.
In your log when you upgrade, normally there will be two references to
c
Hello WiX experts,
Could you please have a look at my problem below?
Basically, what I'd like to do is simple. Say, we have the product version 3.1
and 3.2. When install 3.2 on top of 3.1, the 3.1 needs to be removed firstly.
By using Major Upgrade, it works.
Now, we'd like to do one more thing:
By the way, the version 3.1 and 3.2 have the same upgrade ID because they are
3.x products.
The version 2.1 has a different upgrade ID because it's 2.x products.
You can see the upgrade ID is different here:
NEWAPPFOUND
NEWAPPFOUND
Thanks.
From: li
I think your execute sequence needs to be something like:
PREVIOUSFOUND
PREVIOUSFOUND
PREVIOUSFOUND
PREVIOUSFOUND
PREVIOUSFOUND
PREVIOUSFOUND
Neil
-Original Message-
From: Jiang, Chunyan (GE Healthcare) [mailto:chunyan.ji...@ge.com]
Sent: 25 August 20
Thanks for your answer, I have also made a simple test to read a file from
c:\temp folder (with same error)
Peter Shirtcliffe wrote:
>
> I would guess that on a 64-bit system, Environment.SpecialFolder.System
> points to a 64-bit-specific location which would be different to the
> 32-bit vers
Hi Neil,
Thank you for your suggestion. I added another custom action as David Watson
suggested. It works fine. However, I want to define more than one such custom
action to perform calling executable quietly.
I defined them as:
And in the Execute Seque
Hey all,
Looking for some direction and opinions. I need to create an hands
free (no UI/prompting etc) MSI that installs Web Site and app pool on
IIS 6.0. The catch is that the user info and host header info need to be
derived based on an environment variable on the target machine. I have
10 dif
Hello,
It's not built-in yet. One could extend the Wix Preprocessor to
automatically generate new elements.
Best regards,
Sebastian Brand
Instyler Setup - Creating WiX-based MSI installations, elegantly.
http://www.instyler.com
-Original Message-
From: Jaspreet Nabha [mailto:jaspreet
Thanks to David.
I am sorry that I didn't read your last reply for my question. But I read your
link and tried it today.
The example code in your link is very helpful. I modified a little bit. And it
works!
Thanks a lot!
Chunyan
-Ursprüngliche Nachricht-
Von: David Watson [mailto
I would guess that on a 64-bit system, Environment.SpecialFolder.System
points to a 64-bit-specific location which would be different to the
32-bit version.
I had this problem with SpecialFolder.ProgramFiles where the location
automatically changed from Program Files to Program Files (x86) on
64-b
Hello,
I have a problem with migrating my wix based 32bit msi to windows server
2008 64 bit.
everythink works fine, except file manipulation within a custom action.
I have to modify an IIS configuration file within
%windows%\inetsrv\config\applicationHost.config", but I get a
FileNotFoundExcept
Try appending it to @ApplicationFile
ApplicationFile="Install.exe INSTALLFILE"
I suspect though that it will not work.
Why not make your Install.exe load the parameter from a config file?
Dave
-Original Message-
From: Prabhakaran Paulraj [mailto:prabhakaran_paul...@dynamicbi.com]
Sen
Hi,
I am currently calling an EXE from a bootstrapper which works fine. I need
now to pass a parameter along with the exe.
Eg: Install.exe INSTALL
where INSTALL is the parameter. Is this is possible?
Any help is greatly appreciated.
Below is the code for the Bootstrapper which i am using
Hi All,
I am using WiX3.0 and trying to copy a folder structure to user machine. Th
efolder structure is very huge in depth and i dont want to copy every single
file.
Can you please help me out from this problem.
Thanks
Jaspreet
***The information transmitted is intended only for the person o
Hi Blair,
Thanks for the reply.
I made use of the tip which you gave it works fine partially (i.e)
1) When i run the Install.msi it works as expected (I get the
conditional message which i provided) and the installation stops.
2) When i run the Setup.exe it works as expected (Installation
w
Dear All,
Referring to the documentation "*
http://www.tramontana.co.hu/wix/lesson4.php#4.3*"; :: "*Patchwork*"
I successfully executed instructions up to : light.exe Patch.wixobj.
But when I try to execute the command
*pyro.exe Patch.wixmsp -out Patch.msp -t Sample Patch.wixmst*
I get the Er
Dear All,
Referring to the documentation "*
http://www.tramontana.co.hu/wix/lesson4.php#4.3*"; :: "*Patchwork*"
I successfully executed instructions up to : light.exe Patch.wixobj.
But when I try to execute the command
*pyro.exe Patch.wixmsp -out Patch.msp -t Sample Patch.wixmst*
I get the Er
When sequencing the custom action, use &MyFeature=3 to schedule it whenever
the MyFeature feature is being installed.
Best regards,
Sebastian Brand
Instyler Setup - Creating WiX-based MSI installations, elegantly.
http://www.instyler.com
-Original Message-
From: Yan Sklyarenko [mailto:y
You should set the "same" condition to your custom action as to the
feature. I have quoted the "same" word because the actual condition
might differ between Feature and Custom elements. When feature condition
evaluates to true, it sets the feature level to the value defined in
element. This level
Hello,
I would like to execute custom actions by feature using Wix3.0.
How can I solve this issue?
I means I want to execute a custom action when the dependent feature is
selected.
Does anyone know how to solve and implement it?
Thank you.
Takashi SEKIDO
26 matches
Mail list logo
