True. Still, I would prefer software that would adhere to the target
platform specifications.
Living in an ideal world, I know. I'll stop complaining ;-)
2010/3/31 Curtis Jewell lists.wix-us...@csjewell.fastmail.us
Wilbert - When it's a recompilation for Windows of Unix software, spaces
can
Hi Palbinder Sandher.
Thanks for your answer.
Which language code are you using in your Product Element?
I have the following in the product element:
Product Id=407cffe4-d1ea-452c-a45e-a86a91334f65
Name=$(var.ProductName) Language=1033
Version=$(var.ProductVersion)
Thanks for all the responses so far guys. I have added the custom action
project as a reference to my WiX project and it is now rebuilding the WiX
project correctly when I change the custom action code.
However, what about keeping track of additional files like config files, text
files, etc
Hi,
I'm testing this on my Vista development machine but in the end my
application should run on all OSes starting with Win2k.
I have only one ServiceControl entry, but seems that the problem is not
the service itself but the application that the service babysits, pls
see my answer I just sent
Use a Component Condition on your RemoveFile so it doesn't get
touched during major upgrades.
Thx, I'll do so.
Viv
On 3/29/2010 1:14 PM, Pally Sandher wrote:
What happens if your QA find bugs in your application? Do you fix those
in the installer too?
Use a Component Condition on your
(Unfortunately it's easier said than done and took nearly two major
release cycles for the mindset to catch on here)
Yes, I know, I'm trying to get them understand that. Maybe I'll have
more luck for the next major release.
Thx,
Viv
On 3/30/2010 7:31 AM, Sascha Beaumont wrote:
If you can
Hi,
It's actually a good idea to start with a version lower than I ever
released, so I ended up doing like:
[code]
?define UpgradeCode = GUID?
?define CurrentVersion = 1.0.0?
Upgrade Id=$(var.UpgradeCode)
UpgradeVersion OnlyDetect=no Property=OLDAPPFOUND Minimum=0.0.1
IncludeMinimum=yes
Hi Pally,
I actually wanted to have the upgrade code inside from my very first
version, as this is the way suggested by the WiX tutorial (chapter 4.2):
Also note that this same installer works as a first time installer as
well: if it founds a previous version, it will remove the previous
Posting this in case anyone else runs into this because I'm not sure
if this is a bug or expected behaviour.
I'm updating a plug-in installer to work with a new product which will
be imminently released. After (at least) 4 years of complaining the
developers of said product have caved in
http://wix.sourceforge.net/manual-wix3/patching.htm
Palbinder Sandher
Software Deployment IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the Virtual Environment**
Integrated Environmental Solutions Limited.
You're in the right area with that code. I do something similar for a
plug-in installer using the following:
DirectoryRef Id=CommonAppDataFolder
Directory Id=A_Directory Name=A_Directory
Component Id=A_Component DiskId=1 Guid=A-GUID
RemoveFile Id=Clean_A_Directory
RegSpy2 may be able to help. See
http://www.installsite.org/pages/en/msi/tips.htm about 1/3 down the
page. It'll output a .reg file which you run through tallow.exe to
output WiX code.
However I would ask the vendor of this adxloader.dll for support first.
Palbinder Sandher
Software Deployment
Previously, I have created installers in WiX by hand-writing the .wxs files
myself, but I now have a fairly large folder structure (with lots of
subfolders) to put into an installer, and I am trying to use heat.exe to
harvest this for me. However the harvested file seems unnecessarily messy. Is
Hi,
While trying to do this I got into the problem of setting the correct
condition. So in my case I want a specific file, that it's NOT installed
by the installer, but later created by the user, to be deleted only on
uninstalls - not upgrades, not repairs or modifies. What condition
should I
Hi all,
I asked this question as part of another thread and then just noticed
that it was not the right place as that thread was basically about smth
else, so I'll ask this in a new thread here.
I would like a specific file, that it's NOT installed by the installer,
but later created by the
try
heat.exe harvestType harvester arguments -out sourceFile.wxs
Supported harvesting types:
dir harvest a directory
file harvest a file
project harvest outputs of a VS project
website harvest an IIS web site
Options:
-ag autogenerate component guids at compile
This removes the fragments (I had tried suppressing the fragments already) but
still generates one component per file. Is there any way to set component
generation at folder level rather than at file level?
-Original Message-
From: Tency Kuruvilla [mailto:tency.kuruvi...@kcs.com.kw]
Afraid not that only gets the primary output not referenced assemblies.
Neil
Neil Sleightholm
n...@x2systems.com
On 30 Mar 2010, at 01:20, Bob Arnson b...@joyofsetup.com wrote:
On 3/29/2010 3:56 PM, Neil Sleightholm wrote:
I am afraid that is how heat works, it only finds the primary
We noticed that there must be a bug in LIGHT (WiX 3.0):
We used
HEAT file my.ocx -out my.wxs
to create a Fragment from an OCX file, compiled it using CANDLE, then
tried to link it using LIGHT. LIGHT says that there is a duplicate in
that fragment, so we checked the fragment. In fact,
We're using HEAT to create Fragments from files:
CD %PROGRAMFILES%\Windows Installer XML v3\bin
HEAT file EXCEL8.OLB -gg -out EXCEL8.wxs
That works pretty well as long as HEAT and EXCEL8.OLB are located in the
same folder.
But if they are not, both of the following commands will fail:
Hi,
This is expected behaviour, I have added a registry key with an
keypath=yes in components like this to assuage the ICE gods.
Some people also put a CreateFolder/ element in the component instead
but I like to be very explicit on what my keypaths are.
Dave
-Original Message-
I use the following to show an error message from my C# custom actions:
Record record = new Record();
record.FormatString = My Error;
session.Message(InstallMessage.Error |
(InstallMessage)System.Windows.Forms.MessageBoxIcon.Error |
(InstallMessage)System.Windows.Forms.MessageBoxButtons.OK,
Hello all
I'm having trouble when uninstalling a product that has shared shortcuts
in the startmenu (Shared as in used in more than one product
configuration). It removes all shortcuts that were specific to the
uninstalling product (as well it should) but also removes shortcuts that
are still
We have the following directory structure wherein we want the Logs folder to be
created at the same level as the Services folder.
Directory Id=TARGETDIR Name=SourceDir
Directory Id=SERVICESDIR Name=Services
Directory Id=INSTALLDIR Name=Cmds
. . .
The directory structure below must have a bug in it as it suggest that the Logs
folder is a sibling to Services and not Cmds. Changing the INSTALLDIR property
will only affect the location of the INSTALLDIR directory (Cmds in this case).
If you want to INSTALLDIR to change the location of the
Hi,
With install shield we used to store properties we wanted for later in an xml
file and then install shield would read them in at the beginning of install.
We didn't use a custom action to do this, it was a built in function with
install shield.
I am looking for something similar with
Is the problem that Wix (and heat) aren't in your path?
What I do is:
1. Start a command console
2. Type in path=%path%;C:\Program Files (x86)\Windows Installer XML v3\bin
3. cd to my DLL's location (in your case it would be your OLB file)
4. run heat.
Jeff
We're using HEAT to create
InstallShield provides this functionality via a custom action that was written
by the InstallShield developers.
WiX does not currently ship with a standard custom action to ready property
values from an XML file. If you want this functionality today, you'll need to
write your own custom action
Thanks Dave.
I'll try that.
From: Dave Brotherstone dav...@pobox.com
To: General discussion for Windows Installer XML toolset.
wix-users@lists.sourceforge.net
Sent: Tue, March 30, 2010 10:42:16 PM
Subject: Re: [WiX-users] Wix 2.0: if some dll file(s) deleted,
Sorry, for the typo here is correct structure...
Directory Id=TARGETDIR Name=SourceDir
Directory Id=SERVICESDIR Name=Services
Directory Id=INSTALLDIR Name=Cmds
. . .
/Directory
Directory Id=CANSERVICESLOGFILEDIR Name=Logs
That was a typo, I have structure similar to what you have suggested.
-Original Message-
From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com]
Sent: Wednesday, March 31, 2010 12:43 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users]
Yeah no biggie. I just didn't want to reinvent the wheel.
-Original Message-
From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com]
Sent: Wednesday, March 31, 2010 1:54 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Storing / Accessing
Thanks Palbinder.
Actually we asked the vendor first, but they told us sorry, we don't support
Wix...
Anyways, here I have another question about the conditions:
1. What is the conditions if I'd like to run the custom action in both 'fresh
install' and 'Repair'? Is there something like this?
With this structure you can specify the location of the Services directory
using SERVICESDIR. Doing so will change both Cmds and Logs to be rooted under
SERVICESDIR. You can't change the location of Logs by specifying INSTALLDIR
because INSTALLDIR applies only to Cmds.
Msiexec /I file.msi
Hi
I have a created a wix package to install schedule tasks in windows server.
Once tasks are installed successfully, task should run on particular user
account.
How can I set the user account info to the scheduled task from wix package?
Thanks,
Srinivas
--
View this message in context:
There isn't a built-in way to tell the uninstall that the ServiceControl that
stops the service is going to shut down your app. That means you'll need to use
an uninstall custom action to close down the app - I think WiX has one called
CloseApp or something. You'd sequence this before
Also, what version of the tools are you running? Have you tried 3.0 RTM or a
recent 3.5 weekly release?
-Original Message-
From: s...@pacaccess.com [mailto:s...@pacaccess.com]
Sent: Wednesday, March 31, 2010 10:26 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re:
Does scheduled tasks mean the Task Scheduler interface? Most people doing
this use the standard ITaskScheduler interface (example at
http://www.codeproject.com/KB/system/taskscheduler.aspx, docs at
http://msdn.microsoft.com/en-us/library/aa381811(VS.85).aspx ) and this
includes methods for
We are upgrading our toolset to use .NET 4.0, but I found that light.exe
failed, because it thought that a particular file was not a valid assembly. Not
surprising, since light.exe probably uses standard reflection APIs, and can't
grok a .NET 4.0 binary. Has anyone started building WiX for .NET
How can I create conditions for a custom action to run for Uninstall/Remove
only?
If I use condition 'Installed' then the CA runs in Repair mode.
If I use condition 'Remove=ALL' then the CA doesn't run in Repair, but it
doesn't run in Uninstall/Remove either.
Thanks.
That's because property names are case sensitive and the actual name is REMOVE.
Phil Wilson
-Original Message-
From: little.forest [mailto:little.for...@ymail.com]
Sent: Wednesday, March 31, 2010 3:55 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Conditions for
I don't want to rely on my end users to tell me certain installation
settings. So i decided to make a xml file that that is located in the same
dir as the msi, i then read and parse with custom action, and write those
settings to my users computer.
I just ran into an issue, i was using
Thanks Phil!
That works. Sorry, I didn't pay attention on that.
From: Wilson, Phil phil.wil...@invensys.com
To: General discussion for Windows Installer XML toolset.
wix-users@lists.sourceforge.net
Sent: Wed, March 31, 2010 4:17:59 PM
Subject: Re: [WiX-users]
You'd have this problem even if you weren't using the xml file and instead
provided the property values via the command line. You'll probably want to
store the property values in the registry and use RegistrySearch to get the
saved values.
Edwin G. Castro
Software Developer - Staff
Electronic
On 3/31/2010 8:41 AM, Neil Sleightholm wrote:
Afraid not that only gets the primary output not referenced assemblies.
Aren't they in the content output group?
--
sig://boB
http://joyofsetup.com/
--
Download
On 3/31/2010 6:06 AM, Pally Sandher wrote:
gives the same error (as expected). I can work around this simply by
adding a RegistryValue to each component setting it as the KeyPath for
those components but does anyone know if this is expected behaviour or a
bug with these types of components?
On 3/30/2010 9:11 AM, Trond Andersen wrote:
Directory Id=ProgramFilesFolder
ProgramFilesFolder provides the default. Check a verbose log to see what
MSI thinks the Program Files folder is named.
--
sig://boB
http://joyofsetup.com/
On 3/31/2010 2:31 PM, little.forest wrote:
Actually we asked the vendor first, but they told us sorry, we don't support
Wix...
They don't have to support WiX, just MSI.
--
sig://boB
http://joyofsetup.com/
--
On 3/31/2010 8:55 AM, Markus Karg wrote:
tried to link it using LIGHT. LIGHT says that there is a duplicate in
that fragment, so we checked the fragment. In fact, there is no
duplicate:
What's the exact error message?
--
sig://boB
http://joyofsetup.com/
On 3/31/2010 6:50 PM, Dan Thompson (SBS) wrote:
We are upgrading our toolset to use .NET 4.0, but I found that light.exe
failed, because it thought that a particular file was not a valid assembly.
Not surprising, since light.exe probably uses standard reflection APIs, and
can't grok a .NET
On 3/31/2010 4:07 AM, Michael Bednarek wrote:
However, what about keeping track of additional files like config files, text
files, etc for your application?
There's nothing in WiX to communicate with build systems about the
payloads. Feel free to file a feature request -- or implement it! --
Ok, i can save the data that is in my xml in the registry. But i will need to
do that only the first time.
How do i determine, if this is a first time install ( where i need to read
the xml file) for an advertise install where i need to read the registry.
Should i just have my custom action
Please keep wix-users on the thread so everyone can participate.
You can reschedule overridable custom actions by including them
(optionally with a new condition) in your InstallExecuteSequence (and
other *Sequence elements).
On 3/30/2010 11:13 AM, Christopher Hughes wrote:
Hi Bob,
You
53 matches
Mail list logo
