What is the appropriate way to hande VB6 with dependent projects? The list in ProjectsToBuild doesn't appear to guarantee the build order.
In any case, we'd prefer to explicitly call out the dependencies, along these lines:
<Target Name="BuildDLLs"> <ItemGroup> <ProjectsToBuild Include="utility.vbp;tools.vbp" /> <MSBuild.ExtensionPack.VisualStudio.VB6 TaskAction="Build" Projects="@(ProjectsToBuild)" /> </ItemGroup> </Target> <Target Name="BuildEXEs" DependsOnTargets="BuildDLLs"> <ItemGroup> <ProjectsToBuild Include="mainapp.vbp" /> <MSBuild.ExtensionPack.VisualStudio.VB6 TaskAction="Build" Projects="@(ProjectsToBuild)" /> </ItemGroup> </Target>
But, it builds the DLLs a second time during the BuildEXEs target, which is undesirable for a couple reasons (mainly performance and COM re-re-registration).
Any assistance appreciated!
<TargeName="BuildRootLibs">
<ItemGroup>
<!-- primary libraries (independent of other builds) -->
<!-- bad compat
$(SrcBasePath)\appprofilesupportlib\appprofilesupportlib.vbp;
-->
<ProjectsToBuild Include="
<Target Name="BuildRootLibs">
<ItemGroup>
<!-- primary libraries (independent of other builds) -->
<!-- bad compat
$(SrcBasePath)\appprofilesupportlib\appprofilesupportlib.vbp;
-->
<ProjectsToBuild Include="