My INSTALLDIR property is defined:
When the InstallDirDlg starts, INSTALLDIR property has value "C:\Program
Files\BaseUI\"
I don`t know how I could set initial value of
Hi.
I would like install an XSD file in the VS2005 schema dir.
I looked at how the WiX project found the directory and copied a file
accoridngly (long live open source).
However I expect this part to be in a feature that is installed only
if VS2005 is installed on the target computer. How do I d
Title: Setting Permissions
Welcome to the wonderful world of the 'Permissions'
element.
I
think that You must put it
since we're talking about a directory. Other settings apply
for files or registry-keys.
/Jonas
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of D
Hello
I write installer in WiX for product.
This is new installer and this product already have old versions,
wrote in other installer (NSIS).
I search for older versions like this:
UnsinstallString contains file path for uninstall.exe for older
versions, like "C:\program Files\Solver3
I don't think there are any path manipulation capabilities in MSI, so
you'll have to write a CA that sets INSTALLDIR from OLDINSTALL3 or
OLDINSTALL4.
You can set a property in a CA if it is an immediate (not deferred) CA
using MsiSetProperty. Set the CA's @Execute attribute to
'oncePerProcess'
Can someone help?
Related Question to the UpgradeVersion:
How can I pass a conditional value to a property in a merge
module? I want to be able to tell that property not to install if we are
upgrading.
?'/>
Is it
something like this? Value = ‘
Peter Bocej wrote:
> When the InstallDirDlg starts, INSTALLDIR property has value "C:\Program
> Files\BaseUI\"
> I don`t know how I could set initial value of the PathEdit control.
>
You can tie a PathEdit to a directory property, just don't use
Indirect="yes" unless it's an indirect property.
Jarl Friis wrote:
> However I expect this part to be in a feature that is installed only
> if VS2005 is installed on the target computer. How do I do that?
>
Take a look at the WiX3.msi source. The VS extension includes detection
properties you can use to disable features if VS isn't installed
Thanks Bob, that makes sense and is what I suspected.
As far as using the REINSTALL property, won't that property also be set at times other than a minor upgrade (like a repair)? How does one differentiate between those scenarios? Thanks!
-Tina
- Original Message -From: "Bob Arnson" <[E
Please keep wix-users on the thread.
Rai Wasif wrote:
thanx
for ur suggestion. but i still have problem i.e. after installfile i
call my function but it return with value 1627 i.e. function failed
during installation. if i didn't use any dependend dll function then it
work fine. secon
I don't know the answer but have you seen this: http://www.tramontana.co.hu/wix/lesson5.php#5.12.
I have written a few test installs for COM+ and they all seem to work ok (I
actually wrote this bit of the tutorial). I don't think you need to register the
component first before adding it COM+
I am trying to run a custom action.
Right now that custom action just returns ERROR_SUCCESS but every
invocation fails without even loading the dll.
Here is the log:
Action start
10:58:35: InstallCert.
MSI (s)
(C4:14) [10:58:35:078]: Creating MSIHANDLE (1) of type 790542 for thread
2836
Hi,
I want to add some config handlers to machine.config during
setup so I’m using .
This works fine when I install: the expected elements are
added to machine.config. However, I want these elements to be removed when I
uninstall and I can’t figure out how to do this. My
component looks
Hi all.
I’m using WiX 3.0.2211.0. My installer is pretty
basic, but I have a driver set provided by a partner that I want to have in its
own .WXS, since creating modular installers is a good thing to do. I’ve
attached both .WXS files (redacted and simplified); Product.wxs is the main an
seems missing/SimonOn 10/18/06, Peterson, Joel <[EMAIL PROTECTED]
> wrote:
Hi all.
I'm using WiX 3.0.2211.0. My installer is pretty
basic, but I have a driver set provided by a partner that I want to have in its
own .WXS, since creating modular installers is a good thing to do. I'v
Thanks Neil.
I have been through
the lessons. Unfortunately they're a bit light. However, after posting I
reviewed and managed to figure out part of the issue. Notice below
the "RegisterComPlusAssemblies: DLL: " line is missing anything. I
found a snippet somewhare that clued me to the Dll
Bob Arnson <[EMAIL PROTECTED]> writes:
> Jarl Friis wrote:
>> However I expect this part to be in a feature that is installed only
>> if VS2005 is installed on the target computer. How do I do that?
>>
>
> Take a look at the WiX3.msi source. The VS extension includes
> detection properties you can
Hi All,
Is there a way to pass parameters to function of a library using custom action?
Using the CustomAction I am able to invoke the dll, how do I pass parameters as well?
Thanks,
Kaushik
-
Using Tomcat but need to do m
I have a
This results in
Error LGHT0204: ICE18: KeyPath for Component: 'Comp2' is Directory:
'MyDir'. The Directory/Component pair must be listed in the
CreateFolders table.
According to the documentation, the above should be the way to select
copying a file, by installi
I am trying to run a custom action. Right now that custom action just returns ERROR_SUCCESS but every invocation fails without even loading the dll.
Here is the log:
Action start 10:58:35: InstallCert.
MSI (s) (C4:14) [10:58:35:078]: Creating MSIHANDLE (1) of type 790542 for thread 2836
MSI
Doh!
Yeah,
you’re right. I totally forgot about that. I was working on
and got sidetracked. One thing I don’t understand
is why isn’t a parent node for .
It’d be nice to have exist inside of
or so you wouldn’t have to setup a
with each afterwards.
Oh
well. Thanks for your he
Some thoughts:
Those non-MSI uninstallers often have a quiet switch, so if there's no
need to show the uninstall UI append that to the uninstall string. I
know the InstallShield one does, I'd expect the Wise equivalent to have
the same.
I don't think it's a good idea to have the uninstall custom
So your recommendation is to run the uninstaller as a deferred CA or
just in the InstallExecuteSequence?
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Wilson, Phil
> Sent: Wednesday, October 18, 2006 4:41 PM
> To: wix-users@lists.sourceforge.n
Make sure that is the entry point of the DLL. An exported __stdcall
function is actually decorated to be [EMAIL PROTECTED] so try setting
DllEntry to [EMAIL PROTECTED] If that works, you can
alias the export with the with /EXPORT:[EMAIL PROTECTED]
option on the linker command line.
Use:
dumpbin
you have become a great asset to absolutearts.
You can visit the galley in the middle of nowhere or on this web page.
Our members are in control of their contacts, exposure, sales and
commissions.
All art work and information in your virtual gallery is uploaded and
controlled by you, via our e
Or even better, Heat should have a switch
to throw each directory’s contents into its own .
That would be very cool.
Joel
Peterson
Quality
Assurance Engineer
[EMAIL PROTECTED]
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Peterson,
Joel
Sen
Yes.
1) The general rule is don't change the system in the UI sequence.
Example: I'm thinking the user could go through the UI sequence during
which the older product is uininstalled, and then choose your Cancel
button instead of Install and the older product is now gone.
2) In MSI 4.0/UAC, the
That doesn't seem to be the issue. 'dumpbin /EXPORTS WildcaddySetup.dll' shows:
Microsoft (R) COFF/PE Dumper Version 8.00.50727.42
Copyright (C) Microsoft Corporation. All rights reserved.
Dump of file WildcaddySetup.dll
File Type: DLL
Section contains the following exports for WildcaddySe
Jarl Friis wrote:
> Thanks, it seems like it is all caused by a property will evaluate to
> false if it is set by that cannot find the Registry
> path.
>
Yes, that's it exactly.
--
sig://boB
http://bobs.org
-
Using To
Wilson, Phil wrote:
> 2) In MSI 4.0/UAC, the recommendation is that actions requiring
> privilege (as your uninstall of the older product probably is) should be
> no impersonate/deferred in the execute sequence.
>
More like "must." Only deferred, no-impersonate CAs will get admin privs
when
Peterson, Joel wrote:
Yeah,
you’re right. I totally forgot about that. I was working on
and got sidetracked. One thing I don’t
understand
is why isn’t a parent node for
.
It’d be nice to have exist inside of
or so you wouldn’t have to setup a
with each afterwards.
Pl
Kaushik Barat wrote:
Is
there a way to pass parameters to function of a library using custom
action?
CAs don't take arguments. Instead, you need to set properties to the
arguments you want to pass, then have the CA retrieve the property
values.
--
sig://boB
http://bobs.org
Jarl Friis wrote:
> This results in
> Error LGHT0204: ICE18: KeyPath for Component: 'Comp2' is Directory:
> 'MyDir'. The Directory/Component pair must be listed in the
> CreateFolders table.
>
> According to the documentation, the above should be the way to select
> copying a file, by installing/u
Jeff Jones (HS) wrote:
> That doesn't seem to be the issue. 'dumpbin /EXPORTS WildcaddySetup.dll'
> shows:
>
Take a look at 'dumpbin /imports' -- the most common cause of CAs
failing to load is a missing dependency. CAs in the Binary tables are
extracted to a temporary directory so they don
Stephen Turton wrote:
Hi,
I want to add some config handlers to
machine.config during
setup so I’m using .
This works fine when I install: the expected
elements are
added to machine.config. However, I want these elements to be removed
when I
uninstall and I can’t figure out
Tina Basinger wrote:
>
> As far as using the REINSTALL property, won't that property also be
> set at times other than a minor upgrade (like a repair)? How does one
> differentiate between those scenarios?
>
Well, minor upgrades are implemented as a re-install/re-cache, so I
don't know if the
Joel:
You are missing the for the that will install the
file.
In your case, you would create two folders, but your file would never get
installed.
David Adams
MSN MessengerID: [EMAIL PROTECTED]
From: "Peterson, Joel" <[EMAIL PROTECTED]>
To:
Subject: [WiX-users] Fragments, Cabinets,
Jarl:
Try using the CopyFile in this way:
I believe that CopyFile as a child to a Component element is for a file that
already exists on the machine. In your case, you look to be installing the
file and copying it in your MSI.
David Adams
MSN MessengerID: [EMAIL PROTECTED]
That's exactly the problem. I was accidentally compiling with debug CRTs which
were in the PATH when I ran my test exe but were not when MSI was being run.
The operation I am doing should be run as the person that is doing the
installation. How do I avoid the impersonation?
Thanks for the hel
Jeff Jones (HS) wrote:
> The operation I am doing should be run as the person that is doing the
> installation. How do I avoid the impersonation?
>
The default is to impersonate the user, so you only need
Impersonate="no" when you want the CA to run as LocalSystem.
--
sig://boB
http://bobs.
Stephen,
There were some
challenges to over come with xmlfile about amonth ago – I forget the bug
trackinh numbers but I too had many problems uninstalling xml for web, exe and
machine.config files. I gave up and used a customaction vbs – to my eternal
shame.
br
John
Crouch
Softwar
Hi David.
"david adams" <[EMAIL PROTECTED]> writes:
> Jarl:
>
> Try using the CopyFile in this way:
>
>
>
>
>
>
>
> I believe that CopyFile as a child to a Component element is for a
> file that already exists on the machine.
No, actually the problem cuts down to this:
A produc
control.
>
You can tie a PathEdit to a directory property, just don't use
Indirect="yes" unless it's an indirect property.
--
sig://boB
http://bobs.org
__ Informacia od NOD32 1.1810 (20061018) __
Tat
Thanks John, I’m looking into
doing something similar.
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Crouch,
John
Sent: Wednesday, October 18, 2006 10:32 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] uninstall: removing elements added by
S
Bob Arnson <[EMAIL PROTECTED]> writes:
> Jarl Friis wrote:
>> This results in Error LGHT0204: ICE18: KeyPath for Component:
>> 'Comp2' is Directory:
>> 'MyDir'. The Directory/Component pair must be listed in the
>> CreateFolders table.
>>
>> According to the documentation, the above should be the
45 matches
Mail list logo
