issues run into when converting TFS build to teamcity build
hi, we have a .net web application and we have a tfs build using msbuild which runs successfully and i can build it with visual studio IDE as well on the same machine. but when setting up Teamcity build for the same application it gives quite some challenges. for example, one error is:
WARNING: The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.
also there are issues with wix setup project.
before dive too deep into figuring it out i would like to see if there are any guideline for converting tfs build to teamcity, what needs to be done and what issues can we run into etc. I was initially thinking it is straightforward process but it does not seem that way for me.
thanks for any pointers.
Please sign in to leave a comment.
Hi,
it should be a straightforward process. The error you seem to be getting is quite specific, and if your internal paths to files create a very deep hierarchy, it might be that adding the build agent's path into it leads to exceeding Windows' path size limit.
We don't have a guide on converting TFS to teamcity because it should be indeed pretty much trivial, but it might be that you have hit a hurdle that is uncommon. From the error message you mention, the problem mentioned above would seem to be at the core. You can work around it by specifying an absolute checkout path (ensure that the user running the agent process has permissions to write there) or by moving the build agent to a path closer to the root of the drive.
If there are other issues, you will need to provide more information and error messages.