T4 Toolbox for Visual Studio 2013

Free

Extends Text Templates with syntax colorization, error reporting, outlining, QuickInfo tooltips, statement completion, generation of multiple output files with source control integration, support for template parameters in Solution Explorer properties and more.

(4) Review
Visual Studio
2013
Download (12,027)
11/10/2013
12.10.0.0
View
E-mail Twitter del.icio.us Digg Facebook
Add to favorites
Description
Reviews (4)
Q and A (5)
Sign in to write a review
Sort by:

by k_matsui_ | April 21 2014

by Jimmy Main | January 16 2014

by Peter Kuhn | November 12 2013

Thanks for the update!

by Massimiliano.Donini | November 12 2013

The best syntax highlight extension for T4.

Sign in to start a discussion


  • Color Schemas
    3 Posts | Last post July 21, 2014
    • I am using a dark color schema.  I simply can't read template files in this schema with this extension.  Is there a way to change the color highlighting?
      
    • - did you ever figure out how to alter the syntax colors? I need the same solution.
    • Nevermind... stupid me... just find the Text Template color values under Fonts and Colors.
      
      -- ignore me
  • Settings not shown correctly in settings screen and tangible syntaxhighlighting trouble
    1 Posts | Last post May 01, 2014
    • Hi Oleg,
      
      Thanks for a great tool, we use it a lot and find it very useful.
      
      But we have two issues with it, that when I look back at the older versions of t4toolbox are in the product for a while now. It would be a great if you could fix it.
      
      The first issue that the t4 tool box still not works nicely with the tangible t4 syntax highlighting. For me on a daily and solution basis I need to close my solution, disable t4toolbox, restart VS, enable t4toolbox restart VS, open solution to get the syntax highlighting to work. 
      
      The second issue is that the setting screen does not show the correct values for the options when looking at the registry the setting has been set correctly but the settings screen just shows the default values ( https://t4toolbox.codeplex.com/workitem/24427 ) I think this might relate to issue 1
      
      I use VS2013 update 1 with resharper on a 64 bit windows 7 laptop.
  • source?
    1 Posts | Last post January 16, 2014
    • Hi Oleg,
      
      The original T4 toolbox was open source, and located at codeplex.
      Are you considering updating the source with this new version, or better still adding this version to github?
      
      Will it remain closed?
      I am really hoping that you open it up again... Either way it's a useful plugin.
  • .t4 file extension support for code templates
    1 Posts | Last post November 19, 2013
    • This extension may serve a different purpose then what I have in mind, but upon installing I expected to be able to edit *.t4 files with syntax highlighting. Am I missing something? Are there plans to support *.cs.t4 files?
      
      Thanks,
      Jeremy
  • Compiling transformation
    2 Posts | Last post November 16, 2013
    • Hello,
      
      In previous version of T4Toolbox (v10) I used custom transformation property and access it as follow:
      TransformationContext.Transformation.MyProperty
      
      Now the TransformationContext now implements the Singleton pattern, so I should be able to access it as follow
      TransformationContext.Current.Transformation.MyProperty
      
      but now received the following error:
      
      Compiling transformation: 'Microsoft.VisualStudio.TextTemplating.TextTransformation' does not contain a definition for 'MyProperty' and no extension method 'MyProperty' accepting a first argument of type 'Microsoft.VisualStudio.TextTemplating.TextTransformation' could be found (are you missing a using directive or an assembly reference?)	
      
      Thanks,
      NEMAK
      
      
      
    • Nemak, You're right; this was lost in the upgrade from v10 to v11. As an alternative, you can use the Session property. It is a dictionary shared by the transformation (script) and all of the templates. In other words, in your main transformation you can do this:
      
      this.Session["MyProperty"] = myValue;
      
      and in any of the templates it creates you will be able to access this value the same way:
      
      var myValue = this.Session["MyProperty"];
      
      Hope this helps,
      Oleg