Reputation: 20050
I am trying to setup a process where my T4 templates will be transformed on the build server (Visual Studio is not installed there).
I've read all online references, but could not get a clear source that shows how to do this.
Specifically, here's the 2 issues i've encountered:
C:\TeamCity\buildAgent\work\AppSettings.tt(0,0) : error CS0006: Compiling transformation: Metadata file 'Microsoft.VisualStudio.TextTemplating.Interfaces.10.0, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' could not be found
Registering the DLL files using gacutil fixes this issue, although i would like to avoid this step.
This method helps in determining a full path to the .txt file that is used by the template as its data source. Without it this file can not be found on the build server.
Any help will be appreciated in getting this running.
EDIT: opened an MS CONNECT issue: https://connect.microsoft.com/VisualStudio/feedback/details/744137/texttransform-exe-does-not-work-without-vs2010-installed
References i have checked:
Upvotes: 10
Views: 6601
Reputation: 2882
Copy the following directory from your development machine to the build server.
Source (your machine):
%CommonProgramFiles(x86)%\Microsoft Shared\TextTemplating\<version>.0
Destination (build server):
%CommonProgramFiles(x86)%\Microsoft Shared\TextTemplating\<version>.0
Where <version>
is the most recent version.
Copy all assemblies (.dll) from your development machine to the build server.
Source (your machine):
%WinDir%\Microsoft.NET\assembly\GAC_MSIL\Microsoft.VisualStudio.TextTemplating.*
Destination (build server):
%CommonProgramFiles(x86)%\Microsoft Shared\TextTemplating\<version>.0
Where *
is the rest of the directory name.
Using Gacutil /i install all copied assemblies into GAC of the build server.
Upvotes: 0
Reputation: 2338
Ditch the Microsoft TextTransform.exe and use the free one that ships with MonoDevelop that doesn't have external dependencies.
See here: T4 without Visual Studio?
Upvotes: 1
Reputation: 11577
I believe the issue is that you are using host specific features such ResolvePath.
One way I would try is making sure the templates doesn't use ResolvePath but instead rely on relative paths from a well-known location.
This well-known location could be known by:
1. Convention
2. Environment variable
3. Registry
4. SQL Server
5. Web Service
6. And others
If you don't like the idea of forcing devs setup environment variables I would consider making a "smart" resolvepath that uses the environment variable if available, otherwise relies on Host.ResolvePath.
Hope this helps
Upvotes: 2