| JohnGardnerJr 2004-03-29, 11:50 am |
| We have a number of independent projects that build components that fit into
a system. Some of these components are dependent on each other and so are
added as references to the projects. The problem for us is that we haven't
found a way to make these path relative. We want to use the same automated
build process for both the developers and the build machine. This means
that files will be checked out to different locations and we want them to
build regardless of where they are checked out as long as everything stays
path relative (checkout of all projects to a common root folder)
As a workaround we may write a utility that iterates through the various
projects and does a "fix-up" on the paths or as another possibility write
the dependency files to a temporary folder which we delete after the build.
It isn't an option to create one monolithic solution to encapsulate all the
projects.
So is there a way that references can be path relative to the location of
the project file?
We are using VS 2003 VB.Net, VBDoc, NDoc, NUnit and Visual Build Pro. We
were able to solve all problems regarding paths with the tools but not with
Visual Studio
|