Re: [WiX-users] How to write conditions for 'Change' mode

2012-02-21 Thread sttaq
i feel that the log is useless over here. I think I might be missing out
something. My normal log when I install the complete product shows that a
file has been moved but I can not find even the name of the file anywhere
when I try to install using Change option.

Also note that this thing works if I install the file first on Target Dir
and then Copy it but if I directly try to move it from the Source, without
installing it, nothing happens on Change.

--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-to-write-conditions-for-Change-mode-tp5822126p7304293.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] How to write conditions for 'Change' mode

2012-02-20 Thread sttaq
Hi
I am stuck in a similar situation. However my problem is related to the
execution of CopyFile on change/repair. 

I have a feature which has a component which copies/moves a file from the
source folder to a folder already present somwhere inside a users system. It
is not the folder of my application. I am only moving this file and not
installing it to the the target. This feature works fine if I install it
using a complete setup. But when on initial install I chose not to install
this feature and then try to install it during a  change  all other custom
actions/components inside the feature are executed/installed except for the
CopyFile component. This is critical to my setup and if it does not get
copied my setup will fail. 

Just wondering if anyone found a solution to the problem in this thread or
came across a similar issue?

--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-to-write-conditions-for-Change-mode-tp5822126p7301287.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-dev2
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] How to write conditions for 'Change' mode

2012-02-20 Thread Rob Mensching
A verbose log file should explain.

On Mon, Feb 20, 2012 at 5:37 AM, sttaq tt...@hotmail.com wrote:

 Hi
 I am stuck in a similar situation. However my problem is related to the
 execution of CopyFile on change/repair.

 I have a feature which has a component which copies/moves a file from the
 source folder to a folder already present somwhere inside a users system.
 It
 is not the folder of my application. I am only moving this file and not
 installing it to the the target. This feature works fine if I install it
 using a complete setup. But when on initial install I chose not to install
 this feature and then try to install it during a  change  all other
 custom
 actions/components inside the feature are executed/installed except for the
 CopyFile component. This is critical to my setup and if it does not get
 copied my setup will fail.

 Just wondering if anyone found a solution to the problem in this thread or
 came across a similar issue?

 --
 View this message in context:
 http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-to-write-conditions-for-Change-mode-tp5822126p7301287.html
 Sent from the wix-users mailing list archive at Nabble.com.


 --
 Try before you buy = See our experts in action!
 The most comprehensive online learning library for Microsoft developers
 is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
 Metro Style Apps, more. Free future releases when you subscribe now!
 http://p.sf.net/sfu/learndevnow-dev2
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users




-- 
virtually, Rob Mensching - http://RobMensching.com LLC
--
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-dev2
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] How to write conditions for 'Change' mode

2010-12-15 Thread little.forest
I'm not sure if the email was sent correctly or not. Just resend it.


~~
Thanks Blair.


It's in InstallExecuteSequence. And it's before InstallFinalize.

Here's the code:
CustomAction Id=DoDllRegistration
FileKey=FileRegistrator
ExeCommand=/r
Execute=deferred
Return=ignore
HideTarget=no
Impersonate=no /

InstallExecuteSequence
Custom Action=DoDllRegistration Before=InstallFinalize (NOT REMOVE ~= 
ALL) AND (amp;Feature_XYZ = 3)/Custom
/InstallExecuteSequence



Thanks.





From: little.forest little.for...@ymail.com
To: General discussion for Windows Installer XML toolset. 
wix-users@lists.sourceforge.net
Sent: Mon, December 13, 2010 3:24:19 PM
Subject: Re: [WiX-users] How to write conditions for 'Change' mode

Thanks Blair.


It's in InstallExecuteSequence. And it's before InstallFinalize.

Here's the code:
CustomAction Id=DoDllRegistration
FileKey=FileRegistrator
ExeCommand=/r
Execute=deferred
Return=ignore
HideTarget=no
Impersonate=no /

InstallExecuteSequence
Custom Action=DoDllRegistration Before=InstallFinalize (NOT REMOVE ~= 
ALL) AND (amp;Feature_XYZ = 3)/Custom
/InstallExecuteSequence



Thanks.




From: Blair os...@live.com
To: General discussion for Windows Installer XML toolset. 
wix-users@lists.sourceforge.net
Sent: Fri, December 10, 2010 11:57:29 PM
Subject: Re: [WiX-users] How to write conditions for 'Change' mode

In what sequence is your custom action (execute, or ui)?

Where in that sequence is it scheduled (before CostInitialize, after
CostFinalize, before or after InstallInitialize, before or after
InstallFinalize)?

-Original Message-
From: little.forest [mailto:little.for...@ymail.com] 
Sent: Friday, December 10, 2010 12:00 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] How to write conditions for 'Change' mode

Hi Blair,


Thanks for your reply.

We'd like to detect whenever the user adds the feature XYZ.

Basically, we have a component which is an Outlook plugin. During
installation, 
the user can choose install it or not. If the user doesn't install it in
initial 
install, then she can add it in Change mode. There is an old post about 
this(http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Feature-h
ow-to-reinstall-it-or-uninstall-it-alone-td5608464.html#a5608786
).

After enabling the Change button, the user can install the feature by
hitting 
the Change button. But after that, the dll wasn't registered. From log, I 
learnt the CA is skipped. So I thought the condition wasn't correct. So I'd
like 
to do the registration CA in Change mode, and of course, this happens only
if 
the user really install the component. I thought there is some condition
like 
(NOT Installed) OR (InstallMode = 'Change'). But there is no such thing.

So is this correct? Or there should be some other decent solution?
Custom Action=DoDllRegistration Before=InstallFinalize (NOT REMOVE ~= 
ALL) AND (amp;Feature_XYZ = 3)/Custom

Thanks.




From: Blair os...@live.com
To: General discussion for Windows Installer XML toolset. 
wix-users@lists.sourceforge.net
Sent: Fri, December 10, 2010 9:57:26 AM
Subject: Re: [WiX-users] How to write conditions for 'Change' mode

What are you trying to do in change mode? Detect whenever the user adds
Feature_XYZ? Or detect anytime it is either added or stays?

It's hard to write conditions when you don't know the scenario.

-Original Message-
From: little.forest [mailto:little.for...@ymail.com] 
Sent: Thursday, December 09, 2010 10:25 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] How to write conditions for 'Change' mode

Hi all,

We have a customaction:
  Custom Action=DoDllRegistration Before=InstallFinalize (Not 
Installed) AND (amp;Feature_XYZ = 3)/Custom

This works in initial install, but not in 'Change' mode. 

From 
here(http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/InstallMo
de-Conditions-DON-T-work-td707286.html
), I learnt that there is no such standard property, and See Examples
of 
Conditional Statement Syntax for how you should do it. 

So I googled and found 
this: http://wix.mindcapers.com/wiki/Conditional_Inner_Text.
!-- Run on initial install, repair and minor upgrade -- Condition 
Message='Blah'COMPANYDIR AND NOT REMOVE ~= ALL/Condition
Even if it doesn't say 'Change' mode, I still gave it a try. This statement 
seems working in 'Change' mode:
  Custom Action=DoDllRegistration Before=InstallFinalize (NOT 
REMOVE ~= ALL) AND (amp;Feature_XYZ = 3)/Custom


So the question is, is this the right thing to do? Is there any potential
risk 
that could blow our current stuff?
How to write the correct condition for initial install and 'Change' mode?

Thanks!


--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https

Re: [WiX-users] How to write conditions for 'Change' mode

2010-12-13 Thread little.forest
Thanks Blair.


It's in InstallExecuteSequence. And it's before InstallFinalize.

Here's the code:
CustomAction Id=DoDllRegistration
FileKey=FileRegistrator
ExeCommand=/r
Execute=deferred
Return=ignore
HideTarget=no
Impersonate=no /

InstallExecuteSequence
Custom Action=DoDllRegistration Before=InstallFinalize (NOT REMOVE ~= 
ALL) AND (amp;Feature_XYZ = 3)/Custom
/InstallExecuteSequence



Thanks.




From: Blair os...@live.com
To: General discussion for Windows Installer XML toolset. 
wix-users@lists.sourceforge.net
Sent: Fri, December 10, 2010 11:57:29 PM
Subject: Re: [WiX-users] How to write conditions for 'Change' mode

In what sequence is your custom action (execute, or ui)?

Where in that sequence is it scheduled (before CostInitialize, after
CostFinalize, before or after InstallInitialize, before or after
InstallFinalize)?

-Original Message-
From: little.forest [mailto:little.for...@ymail.com] 
Sent: Friday, December 10, 2010 12:00 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] How to write conditions for 'Change' mode

Hi Blair,


Thanks for your reply.

We'd like to detect whenever the user adds the feature XYZ.

Basically, we have a component which is an Outlook plugin. During
installation, 
the user can choose install it or not. If the user doesn't install it in
initial 
install, then she can add it in Change mode. There is an old post about 
this(http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Feature-h
ow-to-reinstall-it-or-uninstall-it-alone-td5608464.html#a5608786
).

After enabling the Change button, the user can install the feature by
hitting 
the Change button. But after that, the dll wasn't registered. From log, I 
learnt the CA is skipped. So I thought the condition wasn't correct. So I'd
like 
to do the registration CA in Change mode, and of course, this happens only
if 
the user really install the component. I thought there is some condition
like 
(NOT Installed) OR (InstallMode = 'Change'). But there is no such thing.

So is this correct? Or there should be some other decent solution?
Custom Action=DoDllRegistration Before=InstallFinalize (NOT REMOVE ~= 
ALL) AND (amp;Feature_XYZ = 3)/Custom

Thanks.




From: Blair os...@live.com
To: General discussion for Windows Installer XML toolset. 
wix-users@lists.sourceforge.net
Sent: Fri, December 10, 2010 9:57:26 AM
Subject: Re: [WiX-users] How to write conditions for 'Change' mode

What are you trying to do in change mode? Detect whenever the user adds
Feature_XYZ? Or detect anytime it is either added or stays?

It's hard to write conditions when you don't know the scenario.

-Original Message-
From: little.forest [mailto:little.for...@ymail.com] 
Sent: Thursday, December 09, 2010 10:25 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] How to write conditions for 'Change' mode

Hi all,

We have a customaction:
  Custom Action=DoDllRegistration Before=InstallFinalize (Not 
Installed) AND (amp;Feature_XYZ = 3)/Custom

This works in initial install, but not in 'Change' mode. 

From 
here(http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/InstallMo
de-Conditions-DON-T-work-td707286.html
), I learnt that there is no such standard property, and See Examples
of 
Conditional Statement Syntax for how you should do it. 

So I googled and found 
this: http://wix.mindcapers.com/wiki/Conditional_Inner_Text.
!-- Run on initial install, repair and minor upgrade -- Condition 
Message='Blah'COMPANYDIR AND NOT REMOVE ~= ALL/Condition
Even if it doesn't say 'Change' mode, I still gave it a try. This statement 
seems working in 'Change' mode:
  Custom Action=DoDllRegistration Before=InstallFinalize (NOT 
REMOVE ~= ALL) AND (amp;Feature_XYZ = 3)/Custom


So the question is, is this the right thing to do? Is there any potential
risk 
that could blow our current stuff?
How to write the correct condition for initial install and 'Change' mode?

Thanks!


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



--
Oracle to DB2 Conversion Guide: Learn learn about native support for PL/SQL,
new data types, scalar functions, improved concurrency, built-in packages, 
OCI, SQL*Plus, data movement tools, best practices and more.
http://p.sf.net/sfu/oracle-sfdev2dev 
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
Oracle to DB2 Conversion Guide: Learn learn about native support for PL/SQL,
new data types, scalar functions, improved concurrency, built

Re: [WiX-users] How to write conditions for 'Change' mode

2010-12-11 Thread Blair
In what sequence is your custom action (execute, or ui)?

Where in that sequence is it scheduled (before CostInitialize, after
CostFinalize, before or after InstallInitialize, before or after
InstallFinalize)?

-Original Message-
From: little.forest [mailto:little.for...@ymail.com] 
Sent: Friday, December 10, 2010 12:00 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] How to write conditions for 'Change' mode

Hi Blair,


Thanks for your reply.

We'd like to detect whenever the user adds the feature XYZ.

Basically, we have a component which is an Outlook plugin. During
installation, 
the user can choose install it or not. If the user doesn't install it in
initial 
install, then she can add it in Change mode. There is an old post about 
this(http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Feature-h
ow-to-reinstall-it-or-uninstall-it-alone-td5608464.html#a5608786
 ).

After enabling the Change button, the user can install the feature by
hitting 
the Change button. But after that, the dll wasn't registered. From log, I 
learnt the CA is skipped. So I thought the condition wasn't correct. So I'd
like 
to do the registration CA in Change mode, and of course, this happens only
if 
the user really install the component. I thought there is some condition
like 
(NOT Installed) OR (InstallMode = 'Change'). But there is no such thing.

So is this correct? Or there should be some other decent solution?
Custom Action=DoDllRegistration Before=InstallFinalize (NOT REMOVE ~= 
ALL) AND (amp;Feature_XYZ = 3)/Custom

Thanks.




From: Blair os...@live.com
To: General discussion for Windows Installer XML toolset. 
wix-users@lists.sourceforge.net
Sent: Fri, December 10, 2010 9:57:26 AM
Subject: Re: [WiX-users] How to write conditions for 'Change' mode

What are you trying to do in change mode? Detect whenever the user adds
Feature_XYZ? Or detect anytime it is either added or stays?

It's hard to write conditions when you don't know the scenario.

-Original Message-
From: little.forest [mailto:little.for...@ymail.com] 
Sent: Thursday, December 09, 2010 10:25 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] How to write conditions for 'Change' mode

Hi all,

We have a customaction:
  Custom Action=DoDllRegistration Before=InstallFinalize (Not 
Installed) AND (amp;Feature_XYZ = 3)/Custom

This works in initial install, but not in 'Change' mode. 

From 
here(http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/InstallMo
de-Conditions-DON-T-work-td707286.html
), I learnt that there is no such standard property, and See Examples
of 
Conditional Statement Syntax for how you should do it. 

So I googled and found 
this: http://wix.mindcapers.com/wiki/Conditional_Inner_Text.
!-- Run on initial install, repair and minor upgrade -- Condition 
Message='Blah'COMPANYDIR AND NOT REMOVE ~= ALL/Condition
Even if it doesn't say 'Change' mode, I still gave it a try. This statement 
seems working in 'Change' mode:
  Custom Action=DoDllRegistration Before=InstallFinalize (NOT 
REMOVE ~= ALL) AND (amp;Feature_XYZ = 3)/Custom


So the question is, is this the right thing to do? Is there any potential
risk 
that could blow our current stuff?
How to write the correct condition for initial install and 'Change' mode?

Thanks!


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



--
Oracle to DB2 Conversion Guide: Learn learn about native support for PL/SQL,
new data types, scalar functions, improved concurrency, built-in packages, 
OCI, SQL*Plus, data movement tools, best practices and more.
http://p.sf.net/sfu/oracle-sfdev2dev 
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
Oracle to DB2 Conversion Guide: Learn learn about native support for PL/SQL,
new data types, scalar functions, improved concurrency, built-in packages, 
OCI, SQL*Plus, data movement tools, best practices and more.
http://p.sf.net/sfu/oracle-sfdev2dev 
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--
Oracle to DB2 Conversion Guide: Learn learn about native support for PL/SQL,
new data types, scalar functions, improved concurrency, built-in packages, 
OCI, SQL*Plus, data movement tools, best practices and more.
http://p.sf.net/sfu/oracle-sfdev2dev 
___
WiX-users mailing

Re: [WiX-users] How to write conditions for 'Change' mode

2010-12-10 Thread Blair
What are you trying to do in change mode? Detect whenever the user adds
Feature_XYZ? Or detect anytime it is either added or stays?

It's hard to write conditions when you don't know the scenario.

-Original Message-
From: little.forest [mailto:little.for...@ymail.com] 
Sent: Thursday, December 09, 2010 10:25 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] How to write conditions for 'Change' mode

Hi all,

We have a customaction:
  Custom Action=DoDllRegistration Before=InstallFinalize (Not 
Installed) AND (amp;Feature_XYZ = 3)/Custom

This works in initial install, but not in 'Change' mode. 

From 
here(http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/InstallMo
de-Conditions-DON-T-work-td707286.html
 ), I learnt that there is no such standard property, and See Examples
of 
Conditional Statement Syntax for how you should do it. 

So I googled and found 
this: http://wix.mindcapers.com/wiki/Conditional_Inner_Text.
 !-- Run on initial install, repair and minor upgrade -- Condition 
Message='Blah'COMPANYDIR AND NOT REMOVE ~= ALL/Condition
Even if it doesn't say 'Change' mode, I still gave it a try. This statement 
seems working in 'Change' mode:
  Custom Action=DoDllRegistration Before=InstallFinalize (NOT 
REMOVE ~= ALL) AND (amp;Feature_XYZ = 3)/Custom


So the question is, is this the right thing to do? Is there any potential
risk 
that could blow our current stuff?
How to write the correct condition for initial install and 'Change' mode?

Thanks!


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


--
Oracle to DB2 Conversion Guide: Learn learn about native support for PL/SQL,
new data types, scalar functions, improved concurrency, built-in packages, 
OCI, SQL*Plus, data movement tools, best practices and more.
http://p.sf.net/sfu/oracle-sfdev2dev 
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] How to write conditions for 'Change' mode

2010-12-10 Thread little.forest
Hi Blair,


Thanks for your reply.

We'd like to detect whenever the user adds the feature XYZ.

Basically, we have a component which is an Outlook plugin. During installation, 
the user can choose install it or not. If the user doesn't install it in 
initial 
install, then she can add it in Change mode. There is an old post about 
this(http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Feature-how-to-reinstall-it-or-uninstall-it-alone-td5608464.html#a5608786
 ).

After enabling the Change button, the user can install the feature by hitting 
the Change button. But after that, the dll wasn't registered. From log, I 
learnt the CA is skipped. So I thought the condition wasn't correct. So I'd 
like 
to do the registration CA in Change mode, and of course, this happens only if 
the user really install the component. I thought there is some condition like 
(NOT Installed) OR (InstallMode = 'Change'). But there is no such thing.

So is this correct? Or there should be some other decent solution?
Custom Action=DoDllRegistration Before=InstallFinalize (NOT REMOVE ~= 
ALL) AND (amp;Feature_XYZ = 3)/Custom

Thanks.




From: Blair os...@live.com
To: General discussion for Windows Installer XML toolset. 
wix-users@lists.sourceforge.net
Sent: Fri, December 10, 2010 9:57:26 AM
Subject: Re: [WiX-users] How to write conditions for 'Change' mode

What are you trying to do in change mode? Detect whenever the user adds
Feature_XYZ? Or detect anytime it is either added or stays?

It's hard to write conditions when you don't know the scenario.

-Original Message-
From: little.forest [mailto:little.for...@ymail.com] 
Sent: Thursday, December 09, 2010 10:25 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] How to write conditions for 'Change' mode

Hi all,

We have a customaction:
  Custom Action=DoDllRegistration Before=InstallFinalize (Not 
Installed) AND (amp;Feature_XYZ = 3)/Custom

This works in initial install, but not in 'Change' mode. 

From 
here(http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/InstallMo
de-Conditions-DON-T-work-td707286.html
), I learnt that there is no such standard property, and See Examples
of 
Conditional Statement Syntax for how you should do it. 

So I googled and found 
this: http://wix.mindcapers.com/wiki/Conditional_Inner_Text.
!-- Run on initial install, repair and minor upgrade -- Condition 
Message='Blah'COMPANYDIR AND NOT REMOVE ~= ALL/Condition
Even if it doesn't say 'Change' mode, I still gave it a try. This statement 
seems working in 'Change' mode:
  Custom Action=DoDllRegistration Before=InstallFinalize (NOT 
REMOVE ~= ALL) AND (amp;Feature_XYZ = 3)/Custom


So the question is, is this the right thing to do? Is there any potential
risk 
that could blow our current stuff?
How to write the correct condition for initial install and 'Change' mode?

Thanks!


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


--
Oracle to DB2 Conversion Guide: Learn learn about native support for PL/SQL,
new data types, scalar functions, improved concurrency, built-in packages, 
OCI, SQL*Plus, data movement tools, best practices and more.
http://p.sf.net/sfu/oracle-sfdev2dev 
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--
Oracle to DB2 Conversion Guide: Learn learn about native support for PL/SQL,
new data types, scalar functions, improved concurrency, built-in packages, 
OCI, SQL*Plus, data movement tools, best practices and more.
http://p.sf.net/sfu/oracle-sfdev2dev 
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users