About TypeGen

TypeGen is a command line tool that generates single-class-per-file TypeScript sources from C#. Its primary use case is keeping TypeScript model classes/interfaces in sync with C# models, and for this reason not all C# features are translated to TypeScript (e.g. methods or events will be ignored when generating TypeScript sources).


For .NET Standard compatibility, see compatibility table.

Versions >= 2.0.0

  • CLI (when used from Package Manager console): .NET Core 3.1
  • CLI (when used as a .NET Core CLI tool): .NET Core 2.1, .NET Core 2.2, .NET Core 3.0, .NET Core 3.1
  • Programmatical API: .NET Standard 1.3, .NET Standard 2.0

Versions 1.5.7 - 1.6.7

  • CLI: .NET Core 2.0
  • Programmatical API: .NET Standard versions: 1.3 and 2.0

Versions 1.5.0 - 1.5.6

  • CLI: .NET Framework 4.6
  • Programmatical API: .NET Standard 1.3

Versions <= 1.4.x

.NET Framework 4.0

How to use it

The general idea is: first you select C# types to be generated to TypeScript, then you run the typegen command and the TypeScript files are generated.

The details are covered in the following subsections.

Installing TypeGen

To install TypeGen, add the TypeGen NuGet package to your project. After adding this package, the TypeGen command will be available in the Package Manager console.

You can also use TypeGen as a .NET Core CLI tool, in which case you should install it from this package.

Selecting C# types to generate

C# types to generate can be selected in 2 ways:

  1. By specifying attributes on the C# types you wish to generate.
  2. By creating one or more generation specs (a generation spec is a C# class which specifies which types should be generated) somewhere in your project. To instruct TypeGen to use your generation spec, place this content in a file named tgconfig.json in your project directory:
    "generationSpecs": ["MyGenerationSpec"]

Attributes offer quicker, but more functionally-restricted way of selecting types to generate (recommended for smaller projects), whereas generation specs require more initial work to do, but offer richer functionality (recommended for bigger projects).

After adding attributes or creating/changing generation spec(s), you need to build your project before running the TypeGen command.

Running the TypeGen command

To run TypeGen from the Package Manager console, open the PM console, select your project from the dropdown list and type TypeGen generate or TypeGen -p "MyProjectName" generate (depending on the current working directory of the PM Console; you might have to restart Visual Studio).

To run TypeGen as a .NET Core CLI tool, type dotnet-typegen generate or dotnet-typegen -p "MyProjectName" generate (depending on your current location) in your OS command shell.


Let’s say you have a ProductDto class that you want to export to TypeScript.

  1. If you’re using attributes, annotate your class with an appropriate attribute:
public class ProductDto
    public decimal Price { get; set; }
    public string[] Tags { get; set; }
  1. If you’re using a generation spec, first create your generation spec somewhere in your project:
public class MyGenerationSpec : GenerationSpec
    public MyGenerationSpec()

…and then create a file named tgconfig.json directly in your project folder and place the following content in this file:

    "generationSpecs": ["MyGenerationSpec"]

After finishing instructions described in either 1. or 2., build your project and type TypeGen generate or TypeGen -p "MyProjectName" generate (depending on the current working directory of the PM Console) into the Package Manager Console (you might have to restart Visual Studio). Instead of using the Package Manager Console, you can also use TypeGen as a .NET Core CLI tool by typing dotnet-typegen generate in your OS command shell.

This will generate a single TypeScript file (named product-dto.ts) in your project directory. The file will look like this:

export class ProductDto {
    price: number;
    tags: string[];

What next

More details about the available configuration options (that you can place in tgconfig.json) are described in the CLI section. You can also find out more about attributes or generation specs in their dedicated sections.

If you need to convert between different naming conventions (i.e. your C# code uses different conventions than your TypeScript code), you can utilize the converters functionality.

Instead of using the TypeGen command in the console, you can generate files directly from your code using the TypeGen programmatical API.