Sin descripción

csharptest c2a1f9b538 Unit testing of Packed/Unpacked parsing in Lite hace 14 años
benchmarks 7a66a6d3f4 Benchmark data update. hace 17 años
build 90922db77a Added the field name to all CodedOutputStream.Write??? calls hace 14 años
keys 7a0797f972 added batch for creating a new key hace 14 años
lib 62ce3a625e Added version command to PublishRelease.bat, added use of external signing key hace 14 años
mono 5a80c37842 Moved key file to /keys directory hace 14 años
protos c2a1f9b538 Unit testing of Packed/Unpacked parsing in Lite hace 14 años
src c2a1f9b538 Unit testing of Packed/Unpacked parsing in Lite hace 14 años
testdata d965c666ec line-ending-to-crlf hace 14 años
.gitignore 7691473a71 Completion of 3.5 build integration and Lite runtime build changes. hace 15 años
.hgignore 2503740153 version 2.3.0.277 hace 14 años
license.txt 7f419b131d Added license file hace 15 años
readme.txt 7f419b131d Added license file hace 15 años
todo.txt d965c666ec line-ending-to-crlf hace 14 años

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.