暫無描述

csharptest e1e69ba353 Removed the NoWarn for missing comments 14 年之前
benchmarks 7a66a6d3f4 Benchmark data update. 17 年之前
build 50a89c1c85 Fixed removal of all '_' from names, Added unit test. 14 年之前
keys 7a0797f972 added batch for creating a new key 14 年之前
lib 0f3540e24b Split off the Serialization namespace into a new assembly. 14 年之前
mono 5a80c37842 Moved key file to /keys directory 14 年之前
protos bde57ffc75 Cleanup per review comments. 14 年之前
src e1e69ba353 Removed the NoWarn for missing comments 14 年之前
testdata d965c666ec line-ending-to-crlf 14 年之前
.gitignore 7691473a71 Completion of 3.5 build integration and Lite runtime build changes. 15 年之前
.hgignore 2503740153 version 2.3.0.277 14 年之前
license.txt 7f419b131d Added license file 15 年之前
readme.txt 7f419b131d Added license file 15 年之前
todo.txt d965c666ec line-ending-to-crlf 14 年之前

readme.txt

Welcome to the C# port of Google Protocol Buffers, written by Jon Skeet
(skeet@pobox.com) based on the work of many talented people.

For more information about this port, visit its homepage:
http://protobuf-csharp-port.googlecode.com

For more information about Protocol Buffers in general, visit the
project page for the C++, Java and Python project:
http://protobuf.googlecode.com


Release 0.9.1
-------------

Fix to release 0.9:

- Include protos in binary download
- Fix issue 10: incorrect encoding of packed fields when serialized
size wasn't fetched first


Release 0.9
-----------

Due to popular demand, I have built a version of the binaries to put
on the web site. Currently these are set at assembly version 0.9,
and an assembly file version of 0.9. This should be seen as a mark
of the readiness of the release process more than the stability of
the code. As far as I'm aware, the code itself is perfectly fine: I
certainly have plans for more features particularly around making
code generation simpler, but you should feel confident about the
parsing and serialization of messages produced with this version of
the library. Of course, if you do find any problems, *please* report
them at the web site.

Currently the downloadable release is built with the snk file which
is in the open source library. I am considering having a privately
held key so that you can check that you're building against a
"blessed" release - feedback on this (and any other aspect of the
release process) is very welcome.