Sin descripción

ArnoldZokas 89694eccf9 Removed redundant rules from gitignore hace 15 años
benchmarks 7a66a6d3f4 Benchmark data update. hace 17 años
lib 7a9ef8725e Added NUnit 2.2.8.0 to lib hace 16 años
mono 1a79d04d25 Mono build file improvements and readme hace 17 años
protos 706c5f6985 Add option to remove CLSCompliance attribute hace 16 años
src eb1af68201 Add separate obj directory for CF build to avoid corruption. hace 16 años
testdata bceed3c198 Commit earlier deletes hace 17 años
.gitignore 89694eccf9 Removed redundant rules from gitignore hace 15 años
license.txt 7f419b131d Added license file hace 16 años
readme.txt 7f419b131d Added license file hace 16 años
todo.txt 55a212d384 Better support for Compact Framework builds hace 16 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.