In the wix toolset source download, at src\tools\WixTasks\wix200x.targets , in browsing through that file (and other similar .targets files) it lists the various MSBuild Targets which can be "redefined". So when I was trying to understand the wix build process I created a simple EndPointsSequenceTest.targets file and then add an 'imports' statement to the project file (right-click Unload, right-click edit). These messages helped me understand the sequence of the build process. A simpler approach might be to enable verbose logging in VS using Tools\Options\Projects and Solutions\Build and Run.
<Import Project="..\..\Tools\Targets\EndPointsSequenceTest.targets" /> <?xml version="1.0" encoding="utf-8"?> <Project xmlns="http://schemas.microsoft.com/developer/msbuild/2003";> <Target Name="AfterBuild"> <Message Text="Target AfterBuild executed" /> </Target> <Target Name="BeforeRebuild"> <Message Text="Target BeforeRebuild executed" /> </Target> <Target Name="AfterRebuild"> <Message Text="Target AfterRebuild executed" /> </Target> <Target Name="BeforeResolveReferences"> <Message Text="Target BeforeResolveReferences executed" /> </Target> <Target Name="AfterResolveReferences"> <Message Text="Target AfterResolveReferences executed" /> </Target> <Target Name="BeforeCompileAndLink"> <Message Text="Target BeforeCompileAndLink executed" /> </Target> <Target Name="AfterCompileAndLink"> <Message Text="Target AfterCompileAndLink executed" /> </Target> <Target Name="BeforeSigning"> <Message Text="Target BeforeSigning executed" /> </Target> <Target Name="AfterSigning"> <Message Text="Target AfterSigning executed" /> </Target> <Target Name="SignMsm"> <Message Text="Target SignMsm executed" /> </Target> <Target Name="SignCabs"> <Message Text="Target SignCabs executed" /> </Target> <Target Name="SignMsi"> <Message Text="Target SignMsi executed" /> </Target> <Target Name="SignContainers"> <Message Text="Target SignContainers executed" /> </Target> <Target Name="SignBundleEngine"> <Message Text="Target SignBundleEngine executed" /> </Target> <Target Name="SignBundle"> <Message Text="Target SignBundle executed" /> </Target> <Target Name="AfterSigning"> <Message Text="Target AfterSigning executed" /> </Target> <Target Name="BeforeClean"> <Message Text="Target BeforeClean executed" /> </Target> <Target Name="AfterClean"> <Message Text="Target AfterClean executed" /> </Target> <PropertyGroup> <PreBuildEvent>%40echo "Pre-Build Event in VS2010."</PreBuildEvent> </PropertyGroup> <PropertyGroup> <PostBuildEvent>%40echo "Post-Build Event in VS2010."</PostBuildEvent> </PropertyGroup> </Project> In an earlier post in this thread I described a foolish approach for reusing common code using batch scripts and copying wxs files between projects. Creating 'unbound' wixlibs is a much easier approach to manage! -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Build-order-problems-Votive-vs-MSBuild-tp7594932p7596335.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
