This library provides utilities to interact with Google FlatBuffers using the idioms and APIs familiar to .NET developers.

There are three main components that make up this project:

• Serialization: Allows serialization of .NET types to/from the FlatBuffers format
• Schema Generation: Allows generation of an fbs schema from .NET types
• Reflection: A set of utilities which reflect .NET types for use with FlatBuffers

This project is inspired by Marc Gravell's Protobuf-net. The goals of this project are to bring Protobuf-net-like capabilities to the users of FlatBuffers

The Google FlatBuffers project relies on the creation of fbs schema files and code generating language-specific API bindings from them via flatc. The 'canonical' C# API format is been designed for maximum performance and minimal allocations - a core goal of the FlatBuffers project.

However there are times that, as a .NET developer, you wish to use FlatBuffers as a data format and are willing to sacrifice the performance and low-allocation characteristics of the generated API in favour of an API that is more .NET-centric.

Using the features provided by this project, it is possible to declare your FlatBuffers schemas purely as .NET contracts and serialize data to/from FlatBuffers formatted buffers. You can generated fbs schema files directly from these .NET objects and then generate the APIs for other languages using flatc.

The simplest place to start using the library is to declare a struct in C#. This will serialize the object as struct in FlatBuffer format (eg: fields are inline).

	public struct TestStruct
	{
		public int IntProp { get; set; }
	}

We now need to use the FlatBuffersSerializer to serialize an instance of TestStruct into a byte[] in FlatBuffer format.

	var obj = new TestStruct() { IntProp = 42 };	
	var buffer = new byte[32];
	var serializer = new FlatBuffersSerializer();	
	var bytesWritten = serializer.Serialize(obj, buffer, 0, buffer.Length);

This will copy the serialized data to your byte array at the offset you specified (in this case zero).

Now you can deserialize the data in the buffer into a new .NET object of TestStruct type.

	var newObj = serializer.Deserialize<TestStruct>(buffer, 0, bytesWritten);

Declaring a .NET class will (by default) treat the type as a table in FlatBuffer format. This is an object that can contain empty fields and reference types (such as strings).

	public class TestTable
	{
		public int IntProp { get; set; }
		public string Name { get; set; }
	}

As before, we use the FlatBuffersSerializer to serialize an instance of this object to a byte array in FlatBuffer format.

	var obj = new TestTable() { IntProp = 42, Name = "An example name" };	
	var buffer = new byte[64];
	var serializer = new FlatBuffersSerializer();	
	var bytesWritten = serializer.Serialize(obj, buffer, 0, buffer.Length);

This will take care of serializing the string "An example name" to the buffer and emitting a table that references it.

Deserialization follows the same approach as before.

	var newObj = serializer.Deserialize<TestTable>(buffer, 0, bytesWritten);

The FlatBuffersSerializer supports serialization of types derived from ICollection (such as Array, IList and the generic List<> types). As a result it is possible to serialize .NET objects with definitions similar to these:

    public class TestTableWithArrays
    {
        public int[] IntArray{ get; set; }
        public List<int> IntList { get; set; }
    }

These are (de)serialized in the same way as the previous examples.

Given the struct TestStruct1 we declared earlier, it is possible to use FlatBuffersSchemaGenerator to create a FlatBuffersSchema and emit a fbs schema for a series of types.

In this example, we'll emit to a StringBuilder using a StringWriter, but writing to any TextWriter is supported.

	var generator = new FlatBuffersSchemaGenerator();
    var schema = generator.Generate<TestStruct1>();

    var sb = new StringBuilder();
    using (var sw = new StringWriter(sb))
    {
        schema.WriteTo(sw);
    }

The StringBuffer will now contain the following text:

	struct TestStruct1 {
		IntProp:int;
		ByteProp:ubyte;
		ShortProp:short;
	}

In the real world, we will have more complex types, which includes a struct refering to an enum as well as other structs. The FlatBuffersSchema has a dependency resolution phase and will emit a full schema which includes these referenced types.

    public enum VecType
    {
        Index,
        Vertex
    }

    public struct Vec2
    {
        public VecType Type { get; set; }
        public float X { get; set; }
        public float Y { get; set; }
    }
    
    public struct Point
    {
        public Vec2 A { get; set; }
        public Vec2 B { get; set; }
    }

When you call Generate<Point>(), it will resolve the types Vec2 and VecType and emit a fbs schema as follows:

    enum VecType : int {
        Index,
        Vertex
    }

    struct Vec2 {
        Type:VecType;
        X:float;
        Y:float;
    }
    
    struct Point {
        A:Vec2;
        B:Vec2;
    }

When writing the types, it will emit them from root to leaf, ordering them by enum, struct and then table. This way, you wil wind up with enums declared first, then structs and finally tables.

Sometimes, you want to add multiple, unrelated types to your schema. You can do this by calling the AddType<T>() method on the FlatBuffersSchema.

    var generator = new FlatBuffersSchemaGenerator();
    var schema = generator.Create();

    schema.AddType<UnrelatedType1>();
    schema.AddType<UnrelatedType2>();

    var sb = new StringBuilder();
    using (var sw = new StringWriter(sb))
    {
        schema.WriteTo(sw);
    }

This will ensure that the written schema contains both UnrelatedType1 and UnrelatedType2, even though there are no dependencies between them.

This project uses the following type mappings between .NET base types and FlatBuffers.

Vectors (fbs schema: [type]) are represented via .NET arrays (eg: T[]) or ICollection based types such as List<T>.

Strings in .NET are stored natively in UTF-16; however the FlatBuffers spec requires that strings are written in UTF-8 format. The serialization process will handle the string encoding process.

1. Clone the Flatbuffers-net repository.

2. Sync the git submodule to get the flatbuffers source.

     git submodule init
     git submodule update

3. Build the core solution FlatBuffers-net.sln in Visual Studio 2013/2015.

The solution contains 3 projects:

• FlatBuffers.csproj - the .NET port of FlatBuffers referenced in the flatbuffers submodule. It currently uses the 'safe' configuration.
• FlatBuffers-net.csproj - the main FlatBuffers-net code
• FlatBuffers-net.Tests.csproj - an MS Test project containing the unit & integration tests

This project has only been built in Visual Studio 2013/2015 on Windows x64. No other platforms (eg: Mono/Unity/Xamarin) have been verified, although the travis CI build will build under Mono on Linux.

There are no guarantees that the contents of the buffer emitted by the FlatBuffersSerializer will be exactly the same as that of the canonical output, however the buffers should be compatible with each other.

As a result, we are currently using the test oracle approach to verify that the serialization routines emit a buffer that can be read by the canonical C# code that flatc will emit. Likewise, the canonical code is used to emit a buffer to be read by the deserialization routines in this library.

This library is a work in progress, currently in an early stage of development and is not recommended for use in production applications.

It has not been optimized, will have missing/incomplete features and will most likely contain undiscovered bugs.

There is currently very little documentation other than the unit tests and this README.

• Attributes to control reflection (eg: ordering, default values, required fields, etc)
• Serialization/Deserialization of non-struct/table as root
• User-created typemodels (eg: non-reflection)
• Richer fbs schema writer features (namespaces, includes, etc)

For a more detailed roadmap, please see the issues page.

This project uses parts of Google FlatBuffers .NET port to create and interact with FlatBuffers. See the NOTICE for FlatBuffers licensing.

Marc Gravell's Protobuf-net is a key inspiration for the motivation behind this project.