Is there anyway to detect if your MSI is running a Repair instead of an
Install? We currently do an action after InstallFinalize with the condition
NOT INSTALLED and another before RemoveFiles with REMOVE=ALL for
uninstall, would like to make these events not run at all on repair.
And
Hi again,...
Maybe I am wrong, but I think that:
- the 'IAgree' property is evaluated in the UISequence and thus it
must not be all uppercase.
- if you want to evaluate the property in the InstallExecuteSequence
(which is your case) the property should be uppercase and Secure
Property
Ah, but having the built files build to a Release folder isn't the
problem. The problem is the WiX code generated by Heat wants to install
the files TO a folder named Release inside the applications target folder
of the user's machine. In order to install the DLL to the folder I want, I
need to
Hi all,
I am Facing some problems while uninstalling my application.I am Using
WIX2.0.I am expexcting user inputs while uninstalling application. But i
dont have any control on unistallation.
Can any one tell me how to add user input screen while uninstallation ?
--
View this message in
I think you'll have to manually set the uninstall string, which is usually
created for you here:
Key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{ProductGuid}
Name: UninstallString
Rob
vishvas wrote:
Hi all,
I am Facing some problems while uninstalling my
Onto my second WiX conversion, and yet another set of questions arises.
I have a program that has a sample project distributed with it. The sample
project consists of two folders each containing more folders and a set of
about 10 files, for a total of about 100 files.
Reading through the
You need to reference the tasks dll e.g.:
!-- Load the WiX3 tasks --
loadtasks
assembly=${wix.dir}\Microsoft.Tools.WindowsInstallerXml.NAntTasks.dll /
Note: the rebuild flag for the candle task doesn't currently work so you will
need to make sure the wixobj files are deleted before you
If that's literally quoted from your install it's wrong. The
case-sensitive property name is Installed.
Phil Wilson
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Pseudonymic Wannabe
Sent: Friday, May 18, 2007 12:42 AM
To:
Hi guys,
Here's a puzzle for you to consider. I had a big patching issue for one of
my largest packages and have narrowed the issue down to such a degree that I
have created an identicle package that merely installs one single file that
when patched to it's second version, the MSP creation goes
I don't think MsiPublishAssemblies is relevant here. I've been down that
route before wondering if assemblies are in place after
MsiPublishAssemblies but they're not. When I thought about that, it
makes sense because it's a commit that gets the assemblies in place, and
commit things happen at
I'm still learning the ins and outs of WiX. I'm working on trying to
integrate the generation of an MSI into our automated build process, and
was wondering about the possibility of using heat.ext to harvest the
files needed for the features and components for the MSI. I've read a
few archived
Bump, can any one show what I'm doing incorrectly?
Thanks
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Mike
Menaker
Sent: Thursday, May 17, 2007 1:17 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Am I publishing a property
Is there a way that can change a already exist registry value when install and
restore its original value when uninstall?
Thanks,
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of
This is probably more Windows Installer question than a WiX specific.
I have an install with abot 3 GB of files. All it does is copying files and
creating shortcuts.
MSI file has tranforms for several languages, this localization affects only
installer GUI,
set of files is language neutral and
Well that will get me started. Unfortunately, I think I'm going to have a
long way to go. It seems that Crystal Reports is going to just be insane to
get figured out. But thanks for all your help Neil!
Cheers,
Ryan
On 5/18/07, Neil Sleightholm [EMAIL PROTECTED] wrote:
I started here:
Hi:
I had a WiX script that was working fine for daily builds for the past six
months; today, I did something that's causing Light to report
D:\Source\CreativeKiosk3\Builds\Release-Unsecured\CreativeKiosk_3.0.25-33.msi :
fatal error LGHT0010: There was an error importing table: File with file:
Hi,
I'm trying to use UIRef Id=WixUI_InstallDir / and I'm getting the follwing
link error:
error LGHT0112 : Unresolved reference to symbol 'Property:WIXUI_INSTALLDIR' in
section 'Fragment:'.
When I switch to UIRef Id=WixUI_Mondo / instead of UIRef
Id=WixUI_InstallDir / I don't get any link
more specifically, what ACL options should I be using to enable
ALL users on the computer to write and read files from this folder?
The permission element has a user attribute. What should I be
passing to this? Any code snippets in v2 will be appreciated.
Regards,
John
You might want to go one step further and eliminate the cab files
altogether. The installation package as a whole is certainly not
nearly as compact and neat but you might gain some performance not
extracting from the cab.
If the content lends itself to the concept, you could try breaking it
up
I already found the solution for my link error. I added a property named
WIXUI_INSTALLDIR with a value of the ID of the directory the user will specify
and it solved my link error.
Thanks anyway,
Ravit
From: Ravit Shapira
Sent: Friday, May 18, 2007 3:47 PM
To:
I don't think I can avoid compression. It will not fit on DVD.
The same with splitting it in many MSI. It will change user experience.
I need to have a single set of configuration dialogs and then install files.
Speed is esential. I wonder if there are some property settings that can
improve
Not exactly. If you use Heat on a COM DLL, Heat inserts PUT-GUID-HERE for
the GUID so you can do a search/replace as part of the automated build to
keep the GUID correct and always the same for that component.
Other issues are with the directory structure that Heat uses and the fact
that it's
Heat isn’t designed to be used in an automated build process.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott Palmer
Sent: Friday, May 18, 2007 7:10 PM
To: Yexley, Robert (LNG-CON)
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Using heat.exe as part of an
Gareth at Serif wrote:
The file itself is an EXE, built in VisualStudio 2005 with an internal
manifest, later VeriSigned for Vista verification and just under 13MB in
size. Why can't it be patched by binary difference?
I've run into that before using non-executable data files. The closest I
Kevin Fischer wrote:
Actually that was the complete error message:
candle.exe(0,0): Error CNDL0001: Cannot set column 'Action' with a
null value because this is a required field.
Julie hit upon the solution in another reply. I needed to add an Id
attribute to the CustomAction
vishvas wrote:
I am Facing some problems while uninstalling my application.I am Using
WIX2.0.I am expexcting user inputs while uninstalling application. But i
dont have any control on unistallation.
Can any one tell me how to add user input screen while uninstallation ?
Any data needed
Mark Risher wrote:
Candle and Light are version 2.0.4820.
First suggestion: Try upgrading to the latest v2 weekly release
http://wix.sourceforge.net/releases/. That error is caused by a bug in
the compiler or linker that let an invalid value get through to the link
phase.
Can someone
Kevin Fischer wrote:
I looked at the source code and it appears that the actual close
implementation isn't there (or I missed it). This is in V3 of WiX.
Is there a timeframe for implementation of this?
It's just waiting for someone to volunteer to finish the code.
--
sig://boB
Sandip Ghosh wrote:
Is there any built in facility in MSP to support these requirements,
No. MSI's general rule is to never touch user data; any file updated
after installation is considered user data.
There is no
InstallExecuteSequence table for adding custom actions or File table to
Mike Menaker wrote:
Control Id=Next Type=PushButton X=236 Y=243
Width=56 Height=17 Default=yes Disabled=no
Text=$(loc.WixUINext)
Publish Property=ISWEBBOX Value=TRUE1/Publish
Publish Event=NewDialog
Value=[WixUI_WEBConfigToReadyToInstall_Next]/Publish
Matthew Janulewicz wrote:
I have a need to have different default install paths based on a
variable that's set by the user choosing a radio button in a previous
dialog. Has anyone tried something like this? I can't seem to figure
it out.
It seems that INSTALLDIR always defaults to
Kevin Burton wrote:
I am trying to build an update. From the tutorial I gathered that I
must invoke msiexec directly and with the following arguments:
MSI (c) (98:2C) [20:15:42:978]: Command Line: REINSTALL=ALL
REINSTALLMODE=vomus
Only for a minor update. To start out, I'd suggest
32 matches
Mail list logo
