Phil,
Thanks for reply. First thing I would like to mention that my old Installer
is Installshield Non-MSI ans latest is WiX MSI. I have few limitations also.
Both installers TARGETDIR is same. That is why I wanted to execute custom
action before copying my new files otherwise it will uninstall new files. If I
am sequencing custom action before copying file (sequence 750) &
InstallInitialize(sequence 1500) it is not running. I tried to put custom
action in UISequence also but it is not working for me, I am getting error
2762. Here is my custom action code,
.
.
<CustomAction Id='RemoveInstallShield' Execute='deferred'
Property='OLDVERSIONFOUND' ExeCommand='/s
/f1"[#_0369337057924DA3BA5D5AAB83C135EF]"' Return='asyncNoWait'/>
.
.
<Property Id="OLDVERSIONFOUND" Admin="no" Hidden="no" Secure="no">
<DirectorySearch Id="IS_DirSearch" Depth="4"
Path="[ProgramFilesFolder]\InstallShield Installation
Information\{7A06128A-B3D8-4125-9C4D-34BFDA05C9FB}">
<FileSearch Id="IS_FileSearch" Name="setup.exe"/>
</DirectorySearch>
</Property>
.
<InstallUISequence>
.
<Custom Action="RemoveInstallShield" After="ValidateProductID" >NOT
Insstalled> </Custom>
.
.
Regards,
VK
[EMAIL PROTECTED] wrote:
Send WiX-users mailing list submissions to
wix-users@lists.sourceforge.net
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/wix-users
or, via email, send a message with subject or body 'help' to
[EMAIL PROTECTED]
You can reach the person managing the list at
[EMAIL PROTECTED]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of WiX-users digest..."
Today's Topics:
1. Re: Old Installshield upgrade / Remove using MSI Installer
(Wilson, Phil)
2. ICE80: This 64BitComponent [1] uses 32BitDirectory [3]
([EMAIL PROTECTED])
3. heat output inconsistent (Mark Visser)
4. Problem with Registry (Riyaz Mogharabin)
5. EmbeddedChainer and Bootstrappers (Richard Bain)
----------------------------------------------------------------------
Message: 1
Date: Wed, 5 Mar 2008 11:40:40 -0800
From: "Wilson, Phil"
Subject: Re: [WiX-users] Old Installshield upgrade / Remove using MSI
Installer
To: "wix-users@lists.sourceforge.net"
Message-ID:
<[EMAIL PROTECTED]>
Content-Type: text/plain; charset="us-ascii"
If the product was installed with an MSI-based InstallShield solution then your
first approach was the correct one, and if so you should be trying to figure
out why the upgrade failed. Your custom action solution will not work in the
execute sequence, and is not the right thing to do if the original install is
MSI based. A major upgrade should work fine.
If the InstallShield setup is non-MSI, the kind of thing you can do is a custom
action in the UI sequence to uninstall the older product using the
uninstallstring, and a LaunchCondition in the execute sequence based on the
presence of the UninstallString so you can prevent a silent install from
installing on top of the old product.
Phil Wilson
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of V K Gangwar
Sent: Wednesday, March 05, 2008 9:45 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Old Installshield upgrade / Remove using MSI Installer
Guys,
I developed a MSI installer (WiX) for a product was installed through
InstallShield installer. I want when I install through MSI installer it should
upgrade/ remove the old InstallShield. I tried to upgrade but no success. Then
I wrote a custom action in which I am calling a script which removes old
installshield. I want to run this script before copying new installer files. My
problem is I can't call "deferred (in-script)" custom action before
"InstallInitialize" custom action. If I change my cutom action to non deferred
(immediate or other..). custom action doesn't execute.
How I can fix this issue...
Regards,
Vk
________________________________
Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now.
-------------- next part --------------
An HTML attachment was scrubbed...
------------------------------
Message: 2
Date: Wed, 5 Mar 2008 16:52:17 -0500
From:
Subject: [WiX-users] ICE80: This 64BitComponent [1] uses
32BitDirectory [3]
To:
Message-ID:
Content-Type: text/plain; charset="us-ascii"
Hello,
I am building an installer that uses a merge module for 64 bit machines.
The Package element in both the installer and the merge module specify
(Platforms="x64") and each component says (Win64="yes"). However, I
getting the "ICE80 error: This 64BitComponent [1] uses 32BitDirectory
[3]" (where [1] is the offending component and [2] is the offending
directory). For example:
This 64BitComponent MyComp1.XXXX-XXXX-XXXX-XXXX uses 32BitDirectory
INSTALLDIR.XXXX-XXXX-XXXX-XXXX".
Is there something else I can check?
Is there something else I am missing?
How can I validate that the directories are right in orca?
How can I ensure that my dirs are all 64 bit?
In my installer, INSTALLDIR is falling under "Pfiles" (In one case, I
use ".") , as seen in my example/
Thanks,
Robert.
-------------- next part --------------
An HTML attachment was scrubbed...
------------------------------
Message: 3
Date: Wed, 5 Mar 2008 17:44:37 -0500
From: Mark Visser
Subject: [WiX-users] heat output inconsistent
To: wix-users@lists.sourceforge.net
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Is there any particular reason heat creates a ComponentGroup with -
sfrag, and no ComponentGroup without?
Also, with -sfrag, heat creates a top-level Directory tag. Without, it
creates a top-level DirectoryRef tag. DirectoryRef is very useful in a
fragment. Directory, not so much.
It would be fantastic if heat added the ComponentGroup section by
default (or if there were a command-line option for this) without -
sfrag.
cheers,
-Mark
------------------------------
Message: 4
Date: Thu, 6 Mar 2008 02:42:10 +0330
From: "Riyaz Mogharabin"
Subject: [WiX-users] Problem with Registry
To:
Cc: [EMAIL PROTECTED]
Message-ID: <[EMAIL PROTECTED]>
Content-Type: Text/Plain; charset="iso-8859-1"
Dears,
I hope you are fine and doing well.
Thanks for the answers. They really taught me things.
It seems that I can use these when there is no Dialogs. I mean if I write an
installer to copy some files with no dialog shown to user, this works.
But when I put this code into the WiXUI library to use, everything goes
wrong. I mean, I can not assign the Value I get from the registry to the
INSTALLDIR which is used in the WiXUI.InstallDir. Is it possible to use this
option with WiXUI.InstallDir at all? Do I need to set another thing?
(In fact, there will be a problem when we want to show the value to the user
to let him change or accept.)
This will be the error message:
This may indicate a problem with this package. The error code is 2343.>
----------------------------------------------------------------------
Hi,
Read a registry value and assign to a property like so
Root='HKLM'
Key='SOFTWARE\Microsoft\VisualStudio\9.0'
Name='InstallDir'
Type='raw' />
Then you will start your directory structure like so
Note DirectoryID is the same as the property id.o
Regards
Stephen
> Subject: Re: [WiX-users] Problem Reading Registry
>
> Please refer to http://www.tramontana.co.hu/wix/lesson1.php, under
"1.5
> Where to Install?". It contains a really simple and exhaustive
> explanation about this issue.
>
> Hope this helps,
> Boris
>
Original Messages:
> Riyaz Mogharabin wrote:
> > Hi everybody,
> >
> > I have to read a registry value from a specific key ( lets say
> > HKLM\Software\Company\ ) and this value contains the path to the
> location
> > where we need to install the software (so the format of the value
>> Will be something like "C:\Company\HomeDir\" ).
> >
> > How can I get this value by use of Element? How can I
> > assign this value to the Directory where I want to install files in?
> >
> >
> >
> > ">
> >
> >
> >
> >
> >
> > This means, the Value must be divided into the directory names, and
> > be used in the names. But how can I get this value by
>
> > Element, and how can I divide it? Can anybody give me a sample code?
> >
> > Also I must add that I use "wix-2.0.5805.0" as the stable version.
> >
> > Thank you very much,
------------------------------
Message: 5
Date: Thu, 6 Mar 2008 10:50:56 +1100
From: Richard Bain
Subject: [WiX-users] EmbeddedChainer and Bootstrappers
To:
Message-ID:
Content-Type: text/plain; charset="iso-8859-1"
Hi,
I'm trying to recreate an old installshield installer with WiX (I'm still new
to both WiX and Windows Installer). The idea is that the 'core' platform and
the 'apps' section of our program will be split into essentially two serperate
programs with the 'core' part being a prerequisite to install the 'apps'. This
is being done so that each part can be upgraded and patched on its own schedule.
At the moment i'm thinking the only way for this to happen is to have a
seperate msi for each part so obviously I need some kind of bootstrapper or
chainer.
I keep reading that MsiEmbeddedChainer in MSI 4.5 supports chaining multiple
msi's but I can't really find any useful documentation approaching from the WiX
side of things.
Ideally I'd like for the end-user to only see one install process (would be
nice if status message's/overall UI could be controlled). I hear this could be
something to do with 'MsiSetExternalUI' but again, don't know how to approach
this from the WiX side of things.
My questions are:
1) Does EmbeddedChainer suit what I want?
2) If so, is there any examples anywhere of how to use it. Does it need custom
actions or do you literally just pass in another msi (can it even take in
msi's?)
Cheers guys.
_________________________________________________________________
Overpaid or Underpaid? Check our comprehensive Salary Centre
http://a.ninemsn.com.au/b.aspx?URL=http%3A%2F%2Fcontent%2Emycareer%2Ecom%2Eau%2Fsalary%2Dcentre%3Fs%5Fcid%3D595810&_t=766724125&_r=Hotmail_Email_Tagline_MyCareer_Oct07&_m=EXT
-------------- next part --------------
An HTML attachment was scrubbed...
------------------------------
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
------------------------------
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
End of WiX-users Digest, Vol 22, Issue 25
*****************************************
Regards,
Veerendra Gangwar
M +91 94 486 88537
---------------------------------
Never miss a thing. Make Yahoo your homepage.-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
