blob: e88ad552086e8cdbcb45b0600fa36c40f4048862 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
|
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Building Managed Custom Actions</title>
<link rel="stylesheet" type="text/css" href="../styles/presentation.css" />
<link rel="stylesheet" type="text/css" href="ms-help://Hx/HxRuntime/HxLink.css" />
</head>
<body>
<div id="control">
<span class="productTitle">Deployment Tools Foundation</span><br />
<span class="topicTitle">Building Managed Custom Actions</span><br />
<div id="toolbar">
<span id="chickenFeet">
<a href="using.htm">Development Guide</a> >
<a href="managedcas.htm">Managed CAs</a> >
<span class="nolink">Building</span>
</span>
</div>
</div>
<div id="main">
<div id="header">
</div>
<div class="summary">
<p>The build process for managed CA DLLs is a little complicated becuase of the
proxy-wrapper and dll-export requirements. Here's an overview:</p>
<ol>
<li>
<p>Compile your CA assembly, which references WixToolset.Dtf.WindowsInstaller.dll and
marks exported custom actions with a CustomActionAttribute.</p>
<li>
<p>Package the CA assembly, CustomAction.config, WixToolset.Dtf.WindowsInstaller.dll,
and any other dependencies using <b>MakeSfxCA.exe</b>. The filenames of CustomAction.config
and WixToolset.Dtf.WindowsInstaller.dll must not be changed, since
the custom action proxy specifically looks for those files.</p>
</ol>
<p><br>
</p>
<p><b>Compiling</b></p>
<pre><font face="Consolas, Courier New">
csc.exe
/target:library
/r:$(DTFbin)\WixToolset.Dtf.WindowsInstaller.dll
/out:SampleCAs.dll
*.cs
</font></pre>
<p><b>Wrapping</b><pre><font face="Consolas, Courier New">
MakeSfxCA.exe
$(OutDir)\SampleCAsPackage.dll
$(DTFbin)\SfxCA.dll
SampleCAs.dll
CustomAction.config
$(DTFbin)\WixToolset.Dtf.WindowsInstaller.dll
</font></pre>
</p>
<p>Now the resulting package, SampleCAsPackage.dll, is ready to be inserted
into the Binary table of the MSI.</p>
<p><br/>
</p>
<p>For a working example of building a managed custom action package
you can look at included sample ManagedCAs project.</p>
<p><br/>
</p>
<p><br/></p>
<p><b>See also:</b></p>
<ul>
<li><a href="writingcas.htm">Writing Managed Custom Actions</a></li>
<li><a href="caconfig.htm">Specifying the Runtime Version</a></li>
</ul>
<p><br/></p>
</div>
<div id="footer">
<p />
Send comments on this topic to <a id="HT_MailLink" href="mailto:wix-users%40lists.sourceforge.net?Subject=Deployment Tools Foundation Documentation">
wix-users@lists.sourceforge.net</a>
<script type="text/javascript">
var HT_mailLink = document.getElementById("HT_MailLink");
var HT_mailLinkText = HT_mailLink.innerHTML;
HT_mailLink.href += ": " + document.title;
HT_mailLink.innerHTML = HT_mailLinkText;
</script>
<p />
</div>
</div>
</body>
</html>
|
