I’ve been fiddling with setting up automated builds for our old VB6 COM components.
I have successfully installed the MSSCCI provider for TFS 2010 and can successfully check in and check out code from the repository in the Visual Basic IDE.
My repository consists of 1 Team Project (called VB6) with separate directories for each VB6 project.
I’d like to be able to build all the VB6 projects in the Team Project when someone checks in any changes on any of the VB6 projects (I’m sure I can do this by setting up multiple builds in the build definition).
As far as I can tell, there are 2 ways to get this to work:
Editing the Build Template or using the MSBuild Extension Pack
- Will both of these require me to install the VB6 compiler on the build machine?
- Which is the preferred approach for TFS 2010, MSBuild v4?
I prefer the idea of editing the build template than having to install the extension pack.
MSBuild .proj files have been superseeded by windows workflow XAML build templates in VS2010 so I would go with that approach. As far as I know, either way you will have to install Visual Basic on the server as you need the old VB6 compiler.