History

Jon Skeet 541b442b99 Don't create nested types (or field accessors) for map types. I'm sure I've implemented this before, but somehow it's been lost in a maze of twisty little branches, all alike.		2015-07-15 22:04:45 +01:00
..
keys	Imported protobuf-csharp-port into csharp/ tree	2015-04-16 09:55:22 -07:00
protos/extest	Fix for doubly-nested types - issue #307 .	2015-06-29 09:27:54 +01:00
src	Don't create nested types (or field accessors) for map types.	2015-07-15 22:04:45 +01:00
.gitignore	enable building nuget package	2015-07-10 15:23:28 -07:00
build_packages.bat	enable building nuget package	2015-07-10 15:23:28 -07:00
buildall.sh	Fix or delete old projects.	2015-06-26 20:13:05 +01:00
CHANGES.txt	Updated readme.md and changes.txt, removed old license.txt	2015-04-16 10:23:54 -07:00
generate_protos.sh	Generate the well-known types in C#	2015-07-14 14:26:31 +01:00
README.md	Update the readme to give more context of what's going on.	2015-06-19 17:33:20 +01:00

README.md

This directory contains the C# Protocol Buffers runtime library.

Warning: experimental!

This code is still under significant churn. Unlike the original port, it only supports proto3 (but not all of proto3 yet) - there are no unknown fields or extensions, for example. protoc will (eventually) deliberately fail if it is asked to generate C# code for proto2 messages other than descriptor.proto, which is still required for reflection. (It's currently exposed publicly, but won't be eventually.)

Also unlike the original port, the new version embraces mutability - there are no builder types. We plan to add "freezing" operations as well as cloning, however.

Usage

The easiest way to use C# protocol buffers in your project is to use the Google.ProtocolBuffers NuGet package. This package is the legacy package for C# protocol buffers, but it will work fine with C# code generated by protoc if you use proto2 syntax (The API of the runtime library haven't changed so far).

We will definitely release a new NuGet package for the runtime library in the future. The new runtime library WILL contain significant semantic, backwardly-incompatible changes in proto handling (mostly because we will be adding proto3 support and we will be using that oportunity to make some design changes). So keep in mind that you will need to regenerate your proto files and switch to a new NuGet package once the new version of runtime library becomes available.

Building

Open the src/ProtocolBuffers.sln solution in Visual Studio. Click "Build solution" to build the solution. You should be able to run the NUnit test from Test Explorer (you might need to install NUnit Visual Studio add-in).

Supported Visual Studio versions are VS2013 (update 4) and VS2015. On Linux, you can also use Monodevelop 5.9 (older versions might work fine).

History of C# protobufs

This subtree was originally imported from https://github.com/jskeet/protobuf-csharp-port and represents the latest development version of C# protobufs, that will now be developed and maintained by Google. All the development will be done in open, under this repository (https://github.com/google/protobuf).