An MSP is simply a transform which turns one MSI into another MSI. If
you can do it in an MSI, you can do it in an MSP. Simply write your
Custom Action into your new MSI & Condition it with the PATCH property
so it only runs during patching. It should then be run when your MSP is
applied to the target system.

You can't access files inside your cabs until they are installed on the
machine. If you need some functionality of that manner you would need to
use a Binary Element to embed the file itself in your MSI outside of the
cab which can then be used in Custom Actions.

Personally for checks such as the ones your describing, I would use
Launch Conditions to stop the install before it even gets started if the
pre-requisites don't exist on the target machine (to save users & your
QA wasting time waiting for an install to run through which is going to
fail & rollback once it gets to the checks). If you're bootstrapping
those pre-requisites this can be used a "belt and braces" approach to
ensure the install can't continue even if the pre-req installer failed
during your bootstrapper sequence.

Palbinder Sandher 
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500 
F: +44 (0) 141 945 8501 

http://www.iesve.com 
**Design, Simulate + Innovate with the <Virtual Environment>**
Integrated Environmental Solutions Limited. Registered in Scotland No.
SC151456 
Registered Office - Helix Building, West Of Scotland Science Park,
Glasgow G20 0SP
Email Disclaimer

-----Original Message-----
From: Henk Roos [mailto:henk.r...@aricent.com] 
Sent: 16 November 2010 11:54
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] FW: Patching and properties

Thanks Pally for your reply. I'll elaborate a bit more about what we
need. Basically what our client needs is when installing a patch, to
check if certain middleware assembly versions  is installed (which our
client will install). When we make the application build it is not
certain what those middleware assemblies versions will be, so I was
thinking we could pass the version numbers with the patch to the custom
action to check whether they are installed or not, by using properties
or some other means, but I'm getting the feeling that msp's don't
support properties.

Something I just thought about, can a custom action access a file in the
contents cab file of the patch? If it's possible then I can include an
xml file and access that to get the version numbers. Or another thought
I just had is to even install the xml file to a dir and then to run the
custom action after InstallFiles, and the report an error if the
assemblies were not found. What are your thoughts on this?

Regards,

Henk Roos


-----Original Message-----
From: Pally Sandher [mailto:pally.sand...@iesve.com]
Sent: Tuesday 16 November 2010 13:13
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Patching and properties

Patches don't have versions. The version would be the ProductVersion of
the new version your patch is upgrading the old version to.

I don't quite understand your question regarding passing properties to
Custom Actions. Can you elaborate on what you're trying to do?

Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501

http://www.iesve.com
**Design, Simulate + Innovate with the <Virtual Environment>**
Integrated Environmental Solutions Limited. Registered in Scotland No.
SC151456
Registered Office - Helix Building, West Of Scotland Science Park,
Glasgow G20 0SP Email Disclaimer

-----Original Message-----
From: Henk Roos [mailto:henk.r...@aricent.com]
Sent: 16 November 2010 09:39
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Patching and properties

Hi there,

Is it possible to pass a property value somehow to a custom action when
installing a new patch (in stead of passing it with the command line)?
And also I want to know if it is possible to get the patch version being
installed with a custom action. I did run the following command :
"misiexec /update patch.msp /l*v logfile.txt", but I didn't see the a
patch version property somewhere, only the patch description etc

Regards,

Henk Roos


"DISCLAIMER: This message is proprietary to Aricent and is intended
solely for the use of the individual to whom it is addressed. It may
contain privileged or confidential information and should not be
circulated or used for any purpose other than for what it is intended.
If you have received this message in error, please notify the originator
immediately. If you are not the intended recipient, you are notified
that you are strictly prohibited from using, copying, altering, or
disclosing the contents of this message. Aricent accepts no
responsibility for loss or damage arising from the use of the
information transmitted by this email including damage from virus."

------------------------------------------------------------------------
------
Beautiful is writing same markup. Internet Explorer 9 supports standards
for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
Spend less time writing and  rewriting code and more time creating great
experiences on the web. Be a part of the beta today
http://p.sf.net/sfu/msIE9-sfdev2dev
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



------------------------------------------------------------------------
------
Beautiful is writing same markup. Internet Explorer 9 supports standards
for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
Spend less time writing and  rewriting code and more time creating great
experiences on the web. Be a part of the beta today
http://p.sf.net/sfu/msIE9-sfdev2dev
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

"DISCLAIMER: This message is proprietary to Aricent and is intended
solely for the use of the individual to whom it is addressed. It may
contain privileged or confidential information and should not be
circulated or used for any purpose other than for what it is intended.
If you have received this message in error, please notify the originator
immediately. If you are not the intended recipient, you are notified
that you are strictly prohibited from using, copying, altering, or
disclosing the contents of this message. Aricent accepts no
responsibility for loss or damage arising from the use of the
information transmitted by this email including damage from virus."

------------------------------------------------------------------------
------
Beautiful is writing same markup. Internet Explorer 9 supports standards
for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
Spend less time writing and  rewriting code and more time creating great
experiences on the web. Be a part of the beta today
http://p.sf.net/sfu/msIE9-sfdev2dev
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



------------------------------------------------------------------------------
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
Spend less time writing and  rewriting code and more time creating great
experiences on the web. Be a part of the beta today
http://p.sf.net/sfu/msIE9-sfdev2dev
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to