CodeSmith & VS.Net frustrations

time to read 1 min | 107 words

I just spent two hours trying to bring together CodeSmith & VS.Net.
The fault was not in CodeSmith's fault, but VS.Net's.
The problem is that I'm trying to get location independent project, and VS.Net model for running custom tools absolutely forbid it.

It all boils down to Vs.Net running Custom Tools with the current directory set to C:\Program Files\Microsoft Visual Stuido 2003\etc\etc\etc... and not in the current project folder, or the build directory.

What this mean is, I can't have CodeSmith's templates that reference to files in anything but absolute paths, which mean that if I change the project's path, I need to change the CodeSmith property set file.