It's a WiX thing, but a good thing. By adding a reference to the build DLL,
you get the following added in the setup project's wixproj file:
<ItemGroup>
<WixExtension Include="AwesomeExtension">
<HintPath>AwesomeExtension.dll</HintPath>
<Name>AwesomeExtension</Name>
</WixExtension>
</ItemGroup>
Adding the project itself does not add this. Adding a project has uses for
/other/ things. Such as if you want to include the output files of some
project in your installer, you can add the project as a reference and then
use the $(var.MyProjectName.TargetDir) variable to point to that project's
output directory, allowing:
$(var.MyProjectName.TargetDir)MyLibrary.dll
for easy reference to files for use in Components. But for custom
extensions, reference the built assembly.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Noob-creating-a-Custom-Action-in-Wix-3-8-tp7593140p7593195.html
Sent from the wix-users mailing list archive at Nabble.com.
------------------------------------------------------------------------------
Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
With Perforce, you get hassle-free workflows. Merge that actually works.
Faster operations. Version large binaries. Built-in WAN optimization and the
freedom to use Git, Perforce or both. Make the move to Perforce.
http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-users
