Here's a quick example of how you would use a foo.dll method called
foobar.
<Binary Id="FooDll" SourceFile=".\foo.dll" />
<CustomAction Id="DoFooAction" BinaryKey="FooDll" DllEntry="foobar">
<InstallExecuteSequence>
<Custom Action="DoFooAction" After="InstallFiles"/>
</InstallExecuteSequence>
http://www.tramontana.co.hu/wix/
That tutorial is a very good place to start messing around with WiX.
http://www.tramontana.co.hu/wix/lesson3.php#3.3
That section in particular deals with custom actions using dlls.
Brian Poploskie
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of jcafaro10
Sent: Monday, August 06, 2007 2:40 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Beginning Question
Well here's what I have right but still not quite sure about several
things.
What is the wix equivalent of the UsingTask line so it knows to look in
those dll's?
In MSBuild:
<UsingTask TaskName="MSBuild.Community.Tasks.AssemblyInfo"
AssemblyFile="MSBuild.Community.Tasks.dll" />
<UsingTask TaskName="MSBuild.Community.Tasks.Math.Add"
AssemblyFile="MSBuild.Community.Tasks.dll"/>
<UsingTask TaskName="MSBuild.Community.Tasks.Zip"
AssemblyFile="MSBuild.Community.Tasks.dll"/>
<UsingTask TaskName="Sedodream.MSBuild.Tasks.GetAssemblyVersion"
AssemblyFile="Sedodream.MSBuild.Tasks.dll"/>
So far in Wix:
<CustomAction
Id="UpdateAssmebly"
FileKey="not sure what to put here"
Return="ignore" />
<InstallExecuteSequence>
<Custom
Action="UpdateAssmebly"
After="InstallFiles"
<GetAssemblyVersion AssemblyPath="path to exe">
<Output TaskParameter="Major" PropertyName="Major" />
<Output TaskParameter="Minor" PropertyName="Minor" />
<Output TaskParameter="Build" PropertyName="Build" />
<Output TaskParameter="Revision"
PropertyName="CurrentRevision" />
</GetAssemblyVersion>
<!-- Bump up revision number -->
<Add Numbers="$(CurrentRevision);1">
<Output TaskParameter="Result" PropertyName="NewRevision" />
</Add>
<!-- Checkout AssemblyInfo file in preparation for version
increment
-->
<Exec Command=""$(TeamBuildRefPath)\..\tf.exe"
checkout
$(AssemblyInfoFilePath)" />
<!-- Generate new AssemblyInfo file with new version -->
<AssemblyInfo AssemblyCompany="company"
AssemblyCopyright="Copyright"
AssemblyFileVersion="$(Major).$(Minor).$(Build).$(NewRevision)"
AssemblyProduct="product"
AssemblyTitle="title"
AssemblyVersion="$(Major).$(Minor).$(Build).$(NewRevision)"
CodeLanguage="CSharp"
OutputFile="$(AssemblyInfoFilePath)" />
<!-- Checkin AssemblyInfo file to preserve version increment -->
<Exec Command=""$(TeamBuildRefPath)\..\tf.exe" checkin
/comment:"Auto-Build: Version Update" /noprompt
/override:"Auto-Build:Version Update" $(AssemblyInfoFilePath)"
/>>
</Custom>
</InstallExecuteSequence>
Brian Poploskie wrote:
>
> If I understand the question correctly you want to call some methods
> within assemblies during installation? If that's the case you'll want
> to take a look at the CustomAction tag for a type 1 custom action.
>
> To schedule CustomActions after you've created them use the
> InstallExecuteSequence tag and Custom tags underneath that. The after
> and before params point to a step in the sequence. So you could have
a
> custom action that came After="InstallFiles" or
Before="StartServices".
>
> Brian Poploskie
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
jcafaro10
> Sent: Monday, August 06, 2007 12:06 PM
> To: wix-users@lists.sourceforge.net
> Subject: [WiX-users] Beginning Question
>
>
> In our MSBuild proj we have several <UsingTask> lines that link to
some
> assemblies. I'd like to use some of this functionality in my Wix
> Installer
> but unfortunately, copying all of the <UsingTask> lines didn't work
> because
> UsingTask isn't a child of something or other. Any way to get this to
> work?
> --
> View this message in context:
> http://www.nabble.com/Beginning-Question-tf4225049.html#a12019080
> Sent from the wix-users mailing list archive at Nabble.com.
>
>
>
------------------------------------------------------------------------
> -
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems? Stop.
> Now Search log events and configuration files using AJAX and a
browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
------------------------------------------------------------------------
-
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems? Stop.
> Now Search log events and configuration files using AJAX and a
browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
--
View this message in context:
http://www.nabble.com/Beginning-Question-tf4225049.html#a12021902
Sent from the wix-users mailing list archive at Nabble.com.
------------------------------------------------------------------------
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
