VB projects and component references

[a_t_jackson]

This is more of a VB issue but is affecting our Visual Build process...

We have a team of developers working on a VB app that comprises a number of VB components. All components are rebuilt as part of the build process for the main project. We register each component on the build machine as it is built.

It seems that a VB project file (.vbp) stores the path of any components that a project uses. When a developer opens this file in their VB IDE these paths seem to get automatically updated to the location of those components on the developer's machine (VB must read the system registry to do this).

This means that Developer1 might check-in a .vbp containing component paths specific to their machine. When Developer2 then does a GetLatest on this project and opens .vbp in their IDE the paths get autmotically updated to match the COM registration information on their machine. So no problem, Developer2 can still compile the project.

Unfortunately though, Visual Build doesn’t use the VB IDE and so the paths never get automatically updated. This means that the VB compiler on the Visual Build machine attempts to use the paths that were set by the last developer to check-in the .vbp file. If the paths are different the action fails.

This is causing us a lot of problems and so I am wondering if their is anyway to force the Make VB6 action to either update the paths or allow specific paths to be defined for component?