tangible T4 Editor Blog

News, Tip and Tricks from the tangible T4 Editor team.

tangible T4 Editor for VS 2017!


Available for every Visual Studio version since 2008, we are making no exception and release the new version 2.4.0 of our T4 Editor plus modeling tools for Visual Studio 2017!

Model driven development with code generation is a lifestyle here at tangible, so supporting our growing customer base and ever demanding community is our duty.

Let us know how you are using T4 to complete your software projects faster!

tangible T4 Editor for VS 2015!


Today we release the new Version 2.3.0 of our T4 Editor plus modeling tools. This new version includes Visual Studio 2015 support!

Re-Using T4 template for multiple model diagrams


For clarity reasons class models might be split up into multiple diagrams or several class diagrams contribute to the same data model. In this case one would like the T4 template that generates the data model to process all class diagrams at the same time. Unfortunately at the moment a T4 template can only access a single tangible ClassDiagram model using a <#@ TangibleClassDiagram #> directive, so one would have to create a duplicate T4 template for each ClassDiagram. This blog post covers how to process multiple diagrams without maintaining duplicate template code.



We are planning to include access to multiple diagrams in a future release of tangible T4 Editor and modeling tools.

tangible T4 Editor 2.2.0 plus modeling tools – Released!


The new installer routine for our tangible T4 Editor version 2.2.0 gave us a hard fight this time. But finally we could publish the setup files to our download website and to the Visual Studio Gallery on Friday.


Many parts of both the T4 Editor and the modeling tools have been improved taking all of our customers’ feedback into account. Besides several performance and memory optimizations these are the most outstanding new features and improvements:

Add References To Visual Studio Project From T4 Template

This post demonstrates how to add assembly references to the Visual Studio Project the T4 template resides in.



Sometimes the output code generated by a T4 template uses imports from an assembly that has not been referenced by the containing Visual Studio project yet. So on the first build attempt the user receives corresponding compile errors and has to add the references manually.

So why not enable the template to add necessary references to the project while generating the output code?



In order to gain access to the Visual Studio project we use classes from the Visual Studio automation classes. This requires the T4 template to reference the EnvDTE.dll and the VsLangProj.dll. Add the following directives to the header of your template:

Twitter Updates

Authorization on the site

For an authorized user opens up new possibilities