Hi there,

They are just normal files... The CA is linking to a database that has
been copied during install and performing some updates; I've tried
putting it after InstallFiles but it seems to be doing it in some patch
phase rather than after the files have actually been copied which
confused me a lot... 

I could post some exerts from the logfiles if that would help?

Cheers,

Ed Russell
 
CME Product Development Manager
Co-operative IT
 
t: +44 (0) 845 458 5007

m: +44 (0) 7976 055 504

f: +44 (0) 1527 880 975

 
------------------------------------------
CIT email
sender [EMAIL PROTECTED]

-----Original Message-----
From: Derek Cicerone [mailto:[EMAIL PROTECTED] 
Sent: 14 June 2006 16:17
To: Ed Russell; 'Rob Hamflett'; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Sequencing issue

Are the files GACed assemblies or just normal files?  If they are normal
files then you can just schedule your CA after InstallFiles.  What does
your
CA do?

Derek

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Ed Russell
Sent: Wednesday, June 14, 2006 4:08 AM
To: Rob Hamflett; wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Sequencing issue

Totally - I want to get it to run before then so it can roll back but
can't seem to write the file to make it work anywhere else....  

Ed

Ed Russell
 
CME Product Development Manager
Co-operative IT
 
t: +44 (0) 845 458 5007

m: +44 (0) 7976 055 504

f: +44 (0) 1527 880 975

 
------------------------------------------
CIT email
sender [EMAIL PROTECTED]

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Rob
Hamflett
Sent: 14 June 2006 11:19
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Sequencing issue

It doesn't matter if you get it to run when you want, if you sequence it
after InstallFinalize you 
can't roll back the install.  That action commits everything to the
system, so to remove it you'd be 
looking at an uninstall.

Rob

Ed Russell wrote:
> Hi Guys,
> 
> I'm trying to get a custom action DLL execute after the files from the
msi have been installed.  No problem there - I can put it after
InstallFinalize and it works fine.  But I need the install to roll-back
if there is an error code generated by the DLL.  If I try and sequence
it after InstallFiles it runs it in some kind of first pass (doing
patching?) not when the actual files have been copied.  I've started
playing with the "Execute" part of <CustomAction> but it doesn't seem to
give the correct results (I've mostly been experimenting with "deferred"
which appears to run the DLL at the right time but gets a return code
before it looks like it's run it???  I'm very confused and an example of
how to sequence this correctly so that rollback et al works correctly
would be much appreciated.
> 
> Cheers,
> 
> Ed Russell
>  
> CME Product Development Manager
> Co-operative IT
>  
> t: +44 (0) 845 458 5007
> m: +44 (0) 7976 055 504
> f: +44 (0) 1527 880 975
>  
> ------------------------------------------
> CIT email
> sender [EMAIL PROTECTED]
> ________________________________________
> From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Simon
Topley
> Sent: 14 June 2006 10:58
> To: 'Christopher Painter'; [EMAIL PROTECTED];
[EMAIL PROTECTED]
> Cc: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] Extract files from msi (Msiexec,not WIX
issue... .)
> 
> While secretly conversing with Derek I have managed to fix my original
issue. After running MSI validation from Orca I found a strange error
relating to the windows and system folder components... They had no
parent! It seems that WIX allowed it to go through and it does in fact
copy the files to these places... I have now added TARGETDIR as a
directory ref and msiexec /a now extracts all the goodies I want...
meaning I can hopefully just build a patch directly off the back of the
admin install.. woo hoo!
>  
> Thanks for all the help guys, even if we did go a little off track,
it's good to know what other tools are out there as I am sure they will
come in useful at some point.
>  
> Kind Regards
>  
> Simon Topley.
> 
> ________________________________________
> From: Christopher Painter [mailto:[EMAIL PROTECTED] 
> Sent: 14 June 2006 01:55
> To: [EMAIL PROTECTED]; [EMAIL PROTECTED]; 'Simon
Topley'
> Cc: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] Extract files from msi (Msiexec, not WIX
issue... .)
> I agree about VSI MSM's... unfortunatly I'm stuck with about 700 of
them.  I'm also have about 80 MSM's that were statically written using
ORCA because it couldn't be done in VSI and the developer didn't want to
use InstallShield.    
> 
> It was killing me to be storing MSM's in ClearCase so I tried adopting
dark/candle to store XML in ClearCase instead.   Although these merge
modules pass MSM suite validation dark/candle just doesn't like many of
them.  What should be a fairly simple task of creating a round trip
import/export process ends up consuming hours of time.
>  
> BTW that makes me wonder... is there a custom ICE suite available for
running against a database before passing it to Dark?   Basically
business rules enforced by WiX that go beyond the ones in the platform
sdk?
>  
> Chris
> 
> Rob Mensching <[EMAIL PROTECTED]> wrote:
> The PID_REVNUMBER thing sounds like a bug in dark.
> 
> If you have a valid MSI/MSM file I do expect dark.exe to be able to
decompile it.  However, candle appears to be far more exact about what
it allows one to put into an MSI/MSM than some of the other authoring
tools out there (I know this is true about VSI because VSI builds really
horrible MSI files).  Thus, it may be necessary to "fix" the decompiled
source code before being able to recompile it via the WiX toolset.  This
is a great way to clean up "dirty MSI files" (like those that come out
of VSI).
> 
> That said if you build a MSI/MSM (that passes validation) using the
WiX toolset, I do expect to be able to round trip back to source code
then back to MSI/MSM.  My assumption was that Simon was using the WiX
toolset already and thus decompiling should work really well.  Derek
found many bugs in Dark v2 doing this exact process and fixed them in
Dark v3.
> 
> If the tools don't work then please file bugs.  Nobody here pretends
that the WiX toolset is perfect (yet).  If you don't want to help make
the WiX toolset better then that's your decision.  However, I would ask
that you let those who are trying to improve the WiX toolset to
communicate freely here.  This mailing list is about using the WiX
toolset and how it should improve.
> 
> One last thing.  I agree with Derek's analysis about the bug that was
resolved "by design".  However, if you disagree and believe a bug really
needs to be fixed to improve the WiX toolset then the bug should be
discussed here.  The goal is to fix the right bugs the right way not
hurt people's feelings by rejecting their bugs.
> 
> ________________________________________
> From: Christopher Painter [mailto:[EMAIL PROTECTED] 
> Sent: Tuesday, June 13, 2006 9:57 AM
> To: [EMAIL PROTECTED]; [EMAIL PROTECTED]; 'Simon
Topley'
> Cc: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] Extract files from msi (Msiexec, not WIX
issue... .)
> 
> I made this comment because Rob said:
> 
> "Have you looked at dark (the WiX toolset decompiler)?  Dark v3 is
particularly solid.  It will drop all of the files and .wxs authoring in
such a way that the compiler and linker can put it all back together."
> 
> This implied an IJW symbiosis between Dark and Candle and it simply
isn't true. Instead of acknowledging that YMMV in the `real world`, the
MSM to be decompiled is characterized as  `poor authoring`. 
> 
> Here is another example. I have a collection 70 MergeModules ( that
ALL pass validation ).   Each module implements one or many AppSearch
patterns.  Dark fails to extract the PID_REVNUMBER out of the Summary
Information stream on nearly 40% of them.  When I try to candle them
they fail since they don't have  a valid  identifier.    If I look at
the  summary info in Orca they are fine.  If I export and import using
MSI2XML  its fine.  If I merge the modules into an installer it's fine.
> 
> I've really tried to open the door and fit WiX into my existing
installer solution but I just got tired of banging my head against the
wall trying to make it work.  MSI2XML and MSIDB worked just fine without
any effort and I wanted to let Simon know what to expect. 
> 
> 
> Derek Cicerone <[EMAIL PROTECTED]> wrote:
> Christopher,
>     I'm sorry, but I think its a particularly unfair comment to say
that a bug in dark was "scoffed to the side".  I believe the particular
issue you are referring to dealt with dark creating output that when
compiled immediately produced errors.  I would like to explain why that
was done.
>  
> 
> __________________________________________________
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam protection around 
> http://mail.yahoo.com 
> _______________________________________________
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
> 
> __________________________________________________
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam protection around 
> http://mail.yahoo.com 
> 
> 
> 
> <table bgcolor=white style="color:black">
> 
>  
> 
> 
>
-----------------------------------------------------------------------
> This Message has been Scanned by SurfControl(c) Email Filter
>
-----------------------------------------------------------------------
> Co-operative IT is part of The Midcounties Co-operative 
> 
> West Midlands Co-operative Society (WMCS) and Oxford, Swindon and
Gloucester Co-operative Society (OSG) have merged to form The
Midcounties Co-operative.
> 
> The information contained in this e-mail is confidential and is
intended solely for the named recipient(s) only. If you are not the
named recipient(s) you should not disseminate, distribute or copy this
e-mail. If you have received this email in error please notify us by
telephone on (+44 ) 0845 4585 650 immediately and delete the message and
any copies from your computer. The Midcounties Co-operative has taken
every reasonable precaution to ensure that any attachment to this e-mail
has been checked for viruses. However, we cannot accept liability for
any damage sustained as a result of any such software viruses and advise
you to carry out your own virus check before opening any attachment.
Furthermore, we do not accept responsibility for any change made to this
message after it was sent by the sender.
> 
> 
> This Message has been Scanned by SurfControl(c) Email Filter



_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
 


-----------------------------------------------------------------------
This Message has been Scanned by SurfControl(c) Email Filter
-----------------------------------------------------------------------

Co-operative IT is part of The Midcounties Co-operative 

West Midlands Co-operative Society (WMCS) and Oxford, Swindon and
Gloucester
Co-operative Society (OSG) have merged to form The Midcounties
Co-operative.

The information contained in this e-mail is confidential and is intended
solely for the named recipient(s) only. If you are not the named
recipient(s) you should not disseminate, distribute or copy this e-mail.
If
you have received this email in error please notify us by telephone on
(+44
) 0845 4585 650 immediately and delete the message and any copies from
your
computer. The Midcounties Co-operative has taken every reasonable
precaution
to ensure that any attachment to this e-mail has been checked for
viruses.
However, we cannot accept liability for any damage sustained as a result
of
any such software viruses and advise you to carry out your own virus
check
before opening any attachment. Furthermore, we do not accept
responsibility
for any change made to this message after it was sent by the sender.


This Message has been Scanned by SurfControl(c) Email Filter



_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

 

------------------------------------------------------------------------
--------
This Message has been Scanned by SurfControl(c) Email Filter
------------------------------------------------------------------------
--------

Co-operative IT is part of The Midcounties Co-operative 

West Midlands Co-operative Society (WMCS) and Oxford, Swindon and Gloucester 
Co-operative Society (OSG) have merged to form The Midcounties Co-operative.

The information contained in this e-mail is confidential and is intended solely 
for the named recipient(s) only. If you are not the named recipient(s) you 
should not disseminate, distribute or copy this e-mail. If you have received 
this email in error please notify us by telephone on (+44 ) 0845 4585 650 
immediately and delete the message and any copies from your computer. The 
Midcounties Co-operative has taken every reasonable precaution to ensure that 
any attachment to this e-mail has been checked for viruses. However, we cannot 
accept liability for any damage sustained as a result of any such software 
viruses and advise you to carry out your own virus check before opening any 
attachment. Furthermore, we do not accept responsibility for any change made to 
this message after it was sent by the sender.


This Message has been Scanned by SurfControl(c) Email Filter



_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to