Thanks for all answers. This is the final code that worked and I needed to
run
it twice as I had to clean up two directories.
Eitan Behar-3 wrote:
>
> Fixing a little the code below:
>
> use ' instead of " to surround the string value, this is to allow using "
> instead of "e; and t
Hi
While doing installation, I am facing so many errors then on error i want to
roll back all the component which has installed till than.Because if I am
installing very first time and getting some error in between and again try to
install then it is going on Maintenance screen.
Please help me
In article <[EMAIL PROTECTED]>,
"Michael Urman" <[EMAIL PROTECTED]> writes:
> If you're looking for a quick non-debugger method, property changes
> are still logged. It may be a hack, but calling MsiSetProperty(hMSI,
> _T("LOGME"), _T("...")) is effective.
Another option is to call OutputDe
Is this code significantly different than what is in heat? Can we improve heat
as well?
-Original Message-
From: John Hall [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 02, 2008 01:09
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] COM registration
Take a look at the Formatted topic in the MSI SDK. It has all kinds of special
characters to give you feature and component states.
-Original Message-
From: Yuval David [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 02, 2008 06:28
To: WiX-users@lists.sourceforge.net
Subject: [WiX-user
First, you should not be packaging someone else's resources in your MSI. You
should be getting a Merge Module that has all of the COM and DLL and most
importantly the *correct* Component GUIDs. That's what Merge Modules were
designed for. If you're not getting a Merge Module and the producer
That's one of many reasons "SelfReg is evil".
I really should write the blog entry about this... there are just so many
facets it'll take forever.
-Original Message-
From: John Hall [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 02, 2008 03:10
To: General discussion for Windows Inst
Here is an example: http://www.x2systems.com/files/ocx.txt.
The objects I have most problems with are not my own, they are
redistributable components and often Microsoft ones.
I think John Hall may have found the relevant bits to remove, all I need
to do now is find a way of getting that into Hea
Hi Yuval,
If you schedule your custom action after CostFinalize, you can use
$MyComponent=2 condition. This means that component is about to be
uninstalled. You also need to add condition if you don't want your custom
action to run on complete uninstall.
More on feature and component states:
On Thu, Oct 2, 2008 at 3:13 AM, John Hall
<[EMAIL PROTECTED]> wrote:
>> Yeah, Windows Installer doesn't let it work. Why? Some
>> message processing issue inside them. I think this is
>> documented in some small print somewhere.
>>
>> PS: Please don't shoot the messenger.
>
> Of course not. I
Hi,
I'm trying to execute a custom action only after I remove a specific
component (using "Change").
Is there an option to do that? Can I write "Remove="the name of the
component" as a condition for execution of the CA?
Does someone know if it's possible?
Thanks,
Yuval
This is how I generally do it (message box/attach debugger) -- although
you can of course do your own logging.
You could probably even trigger it off of a property passed on the
MSIEXEC command line.
John Hall wrote:
>> Yeah, Windows Installer doesn't let it work. Why? Some
>> message process
> Regarding SelfReg, or not I'm not completely sure I drink
> the Kool-Aid on this one. So, I understand that SelfRegCost
> violates transactability rules (spell checker says
> transactability is not a word >shrug<) due to MSI and how it
> handles that... But what then IS the recommended way t
Regarding SelfReg, or not I'm not completely sure I drink the Kool-Aid
on this one. So, I understand that SelfRegCost violates transactability
rules (spell checker says transactability is not a word >shrug<) due to MSI
and how it handles that... But what then IS the recommended way to deal wit
> Yeah, Windows Installer doesn't let it work. Why? Some
> message processing issue inside them. I think this is
> documented in some small print somewhere.
>
> PS: Please don't shoot the messenger.
Of course not. I had half guessed it was something like this anyway. I guess
it's a matter o
Neil wrote:
> I have tried a
> few times to remove the unrelated code and never successfully
> got the component to work or to leave the machine working on
> uninstall. Have you ever generated the WiX registry code for
> VB6 COM component? Has anyone?
Neil,
I have. I wrote a custom build task tha
Fixing a little the code below:
use ' instead of " to surround the string value, this is to allow using "
instead of "e; and the closing " right after cmd.exe.
http://asp.net/>
Files\myapplication"*'*/>
The generic syntax is:
Eitan
---
17 matches
Mail list logo
