This project is read-only.

VB6 Auto Build with TFS 2010

Jul 29, 2011 at 12:37 AM


Were trying to build a vb6 project using TFS BUILD. The project builds fine except we need it to build the new .ocx based upon the old .ocx(projec compatability). Were using the script below to execute the build. Is there a parameter we need to turn on for compatability mode?



<Project ToolsVersion="4.0" DefaultTargets="Default" xmlns="">   
  <TPath>C:\Program Files\MSBuild\ExtensionPack\4.0\MSBuild.ExtensionPack.tasks</TPath>   
  <TPath Condition="Exists('C:\Program Files (x86)\MSBuild\ExtensionPack\4.0\MSBuild.ExtensionPack.tasks')">C:\Program Files (x86)\MSBuild\ExtensionPack\4.0\MSBuild.ExtensionPack.tasks </TPath> 
 <Import Project="$(TPath)"/>  
  <VBPath>C:\Program Files\Microsoft Visual Studio\VB98\VB6.exe</VBPath>   
  <VBPath Condition="Exists('C:\Program Files (x86)\Microsoft Visual Studio\VB98\VB6.exe')">C:\Program Files (x86)\Microsoft Visual Studio\VB98\VB6.exe</VBPath> 
  <ProjectsToBuild Include="BoldControls.vbp">     
   <!-- Note the special use of ChgPropVBP metadata to change project properties at Build Time -->     
 <Target Name="Default">   
  <!-- Build a collection of VB6 projects -->   
  <MSBuild.ExtensionPack.VisualStudio.VB6 TaskAction="Build" Projects="@(ProjectsToBuild)" VB6Path="$(VBPath)"/> 
 <Target Name="clean">   
  <Message Text="Cleaning - this is where the deletes would go"/>     

Aug 25, 2011 at 6:58 PM

Hi Larry

Any progress? I don't have a vb6 project at hand to try this on, however what you are doing look right to me. Looking at it looks like you may need to pass in CompatibleEXE32 too.