Simplify.Templates 2.0.2

dotnet add package Simplify.Templates --version 2.0.2                
NuGet\Install-Package Simplify.Templates -Version 2.0.2                
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="Simplify.Templates" Version="2.0.2" />                
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add Simplify.Templates --version 2.0.2                
#r "nuget: Simplify.Templates, 2.0.2"                
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
// Install Simplify.Templates as a Cake Addin
#addin nuget:?package=Simplify.Templates&version=2.0.2

// Install Simplify.Templates as a Cake Tool
#tool nuget:?package=Simplify.Templates&version=2.0.2                

Simplify.Templates Documentation

Provides ITemplate interface, Template class and TemplateBuilder class for working with text templates.

With Simplify.Templates you can easily load text templates, localize them, insert data and get generated result.

Available at NuGet as binary package

Quick start

Load the template from a file located in the current assembly directory:

var tpl = TemplateBuilder

The TestTemplate.tpl file:


Setting a data into the template variables:

tpl.Set("SomeVariable", "footext");

tpl.Add("Items", "1")
    .Add("Items", "2")
    .Add("Items", "3");

Getting the template text:

var str = tpl.Get();

str will contain:


Another ways of template loading

To choose how to load template use respective TemplateBuilder static methods:

  • Loading template from a string: FromString("some string")
  • Loading template from a file: FromFile("D:\SomeDir\SomeFile.txt")
  • Loading template from a file located in current assembly directory: FromLocalFile("SomeFile.txt")
  • Loading template from current assembly embedded resources by: FromCurrentAssembly("FilePath.Filename.tpl") or FromCurrentAssembly("FilePath/Filename.tpl")
  • Loading template from specified assembly embedded resources by: FromAssembly("FilePath.Filename.tpl", myAssembly)

Template localization

If you want a template to be localizable then you should create a xml file in the same directory as a template file.

Files should be named like FooTemplate.tpl.en.xml, if a template file name is FooTemplate.tpl. For embedded templates it should be named like FooTemplate.tpl-en.xml.

You can keep several files for each language, which you want to be localized, for example:


Localization file example:

<?xml version="1.0" encoding="utf-8"?>`
    <item name="LocalizableVariable" value="Test" />

Localization file FooTemplate.tpl.en.xml example

<?xml version="1.0" encoding="utf-8"?>`
    <item name="LocalizableVariable" value="Test default" />
    <item name="LocalizableVariable2">
        <a href="#">localizable data default</a>

Template file FooTemplate.tpl example:


To perform localization use respective fluent methods: Localizable, LocalizableFromCurrentThreadLanguage

There are two language code parameters, first is the current language, and seconds is the default language.

At the time when a template builds, the current language localization file will be inserted into the template, after that the default localization file will be inserted. If some localizable values are not exist in the current localization file, then they will be inserted from the default localization file.

To use Thread.CurrentThread.CurrentCulture.TwoLetterISOLanguageName language code as the current language code use LocalizableFromCurrentThreadLanguage method.

Output example:

var tpl = TemplateBuilder
    .Localizable("de", "en")

var str = tpl.Get();

str will contain:

<div><a href="#">localizable data default</a></div>

Building items list example

The MasterTemplate.tpl file:


The FooLinkItem.tpl file:

<a href="http://foolink/{ItemID}">{MyLinkLabel} {ItemID}</a><br />

The FooLinkItem.tpl.en.xml file:

<?xml version="1.0" encoding="utf-8"?>`
    <item name="MyLinkLabel" value="My item" />

Building links list:

class MyItem
    public int ID { get; set; }


var items = new List<MyItem> { {ID = 1}, {ID = 2}, {ID = 3}};

var tpl = TemplateBuilder

var itemTpl = TemplateBuilder

foreach (var item in items)
    itemTpl.Set("ItemID", item.ID);

    // Adding our generated item data to the master template and rolling it back to initial, but localized state
    tpl.Add("Links", itemTpl.GetAndRoll());

var str = tpl.Get();

str will contain:

<a href="http://foolink/1">My item 1</a><br />
<a href="http://foolink/2">My item 2</a><br />
<a href="http://foolink/3">My item 3</a><br />

Model binding example

The MyTemplate.tpl file:


The model:

public class MyClass
    public string Prop1 { get; set; }
    public int Prop2 { get; set; }
    public DateTime Prop3 { get; set; }

Setting model to template:

var obj = new MyClass {Prop1 = "Foo", Prop2 = 5, Prop3 = new DateTime(2014, 09, 13)};

var tpl = TemplateBuilder

tpl.Model(obj).With(x => x.Prop3, x => x.ToString("dd.MM.yyyy")).Set();

var str = tpl.Get();

str will contain:

Product Compatible and additional computed target framework versions.
.NET net5.0 was computed.  net5.0-windows was computed.  net6.0 is compatible.  net6.0-android was computed.  net6.0-ios was computed.  net6.0-maccatalyst was computed.  net6.0-macos was computed.  net6.0-tvos was computed.  net6.0-windows was computed.  net7.0 was computed.  net7.0-android was computed.  net7.0-ios was computed.  net7.0-maccatalyst was computed.  net7.0-macos was computed.  net7.0-tvos was computed.  net7.0-windows was computed.  net8.0 was computed.  net8.0-android was computed.  net8.0-browser was computed.  net8.0-ios was computed.  net8.0-maccatalyst was computed.  net8.0-macos was computed.  net8.0-tvos was computed.  net8.0-windows was computed. 
.NET Core netcoreapp2.0 was computed.  netcoreapp2.1 was computed.  netcoreapp2.2 was computed.  netcoreapp3.0 was computed.  netcoreapp3.1 was computed. 
.NET Standard netstandard2.0 is compatible.  netstandard2.1 is compatible. 
.NET Framework net461 was computed.  net462 was computed.  net463 was computed.  net47 was computed.  net471 was computed.  net472 was computed.  net48 is compatible.  net481 was computed. 
MonoAndroid monoandroid was computed. 
MonoMac monomac was computed. 
MonoTouch monotouch was computed. 
Tizen tizen40 was computed.  tizen60 was computed. 
Xamarin.iOS xamarinios was computed. 
Xamarin.Mac xamarinmac was computed. 
Xamarin.TVOS xamarintvos was computed. 
Xamarin.WatchOS xamarinwatchos was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.
  • .NETFramework 4.8

    • No dependencies.
  • .NETStandard 2.0

    • No dependencies.
  • .NETStandard 2.1

    • No dependencies.
  • net6.0

    • No dependencies.

NuGet packages (2)

Showing the top 2 NuGet packages that depend on Simplify.Templates:

Package Downloads

Lightweight and fast .NET web-framework based on MVC and OWIN


ACSP.NET is a lightweight and fast .NET web-framework based on MVC and OWIN.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last updated
2.0.2 750 5/25/2024
2.0.1 2,004 8/8/2023
2.0.0 20,022 12/8/2019
2.0.0-pre01 406 12/7/2019
1.5.2 2,840 9/28/2019
1.5.1 2,096 6/23/2019
1.5.0 1,770 12/16/2018
1.5.0-pre01 627 11/21/2018
1.4.1 1,190 10/1/2018
1.4.0 1,282 4/12/2018
1.3.0 2,187 8/18/2017
1.2.1 5,397 8/18/2016
1.2.0 1,875 6/1/2015
1.1.2 7,095 10/23/2014
1.1.1 2,027 9/21/2014
1.1.0 2,799 9/2/2014
1.0.5 1,761 8/8/2014
1.0.3 1,421 5/21/2014
1.0.2 1,107 4/23/2014
1.0.0 1,213 2/25/2014