Update to Text Templating syntax for May 2005 CTP

Martin Fowler on Language Workbenches

Stuart Kent's WebLog — Tue, 21 Jun 2005 12:29:58 GMT

Martin has just put up an article on Language Workbenches - IDEs for creating and using DSLs.
As you'd...

My June Backlog - Software Factories Stuff

Rob Caron's Blog — Tue, 05 Jul 2005 03:26:12 GMT

On Language Workbenches:

Martin Fowler’s original post x and additional readings x
Brad Appleton’s...

My June Backlog - Software Factories Stuff

Rob Caron's Blog — Tue, 05 Jul 2005 09:48:59 GMT

On Language Workbenches:

Martin Fowler’s original post &oplus; and additional readings &oplus;...

My June Backlog - Software Factories Stuff

Rob Caron's Blog — Wed, 06 Jul 2005 20:26:56 GMT

On Language Workbenches:

Martin Fowler’s original post ⊕ and additional readings ⊕
Brad Appleton’s...

re: Update to Text Templating syntax for May 2005 CTP

Adam Miller — Fri, 02 Jun 2006 20:15:09 GMT

A caching question: Using the standard templating engine (Microsoft.VisualStudio.TextTemplating.Engine), is there a way to cache the same template file between generations? Specifically, the engine.ProcessTemplate seems to recompile the template each time. Is there a way to cache it? It's taking us minutes to generate 200-300 templates all based on a single template file with different arguments being passed to it.

The code is as easy as: engine.ProcessTemplate(contentStr, new TemplateHost(".", templateArgs).

The T4 engine is fantastic, but becoming harder and harder to work with as we generate more and more. You seem to have lots of good info on this topic, thus my post.

Thanks!

re: Update to Text Templating syntax for May 2005 CTP

Jim Hamilton — Fri, 14 Jul 2006 22:34:04 GMT

I am new to GAT and templating. I was recently assigned to making sure our package still worked with the June release of the GAT. When processing our template, I received the error:

A Statement cannot appear after the first class feature in the template. Only boilerplate, expressions and other class features are allowed after the first class feature block.

I resolved this by moving the class feature block to the end of the template. However, this seems to contradict what you wrote in your April 7th entry:

Limitations
There can only be one class feature block and it must come immediately after the directives.
Code in control blocks has to be C#. We'll add VB.Net support in our next release.

Should class feature blocks now be at the end of the template so that control blocks (in our case a loop) can call a function in the class feature block? Thanks!

T4 Syntax for DSL Tools

GarethJ's WebLog — Tue, 23 Sep 2008 06:48:29 GMT

I've been fielding questions about the syntax of our Text Templating technology (whose codename is "T4")