Chiebot-Mirror
/
protobuf
mirror of https://github.com/protocolbuffers/protobuf.git
8
0
Fork 0
Code Issues Projects Releases Wiki Activity
Protocol Buffers - Google's data interchange format (grpc依赖) https://developers.google.com/protocol-buffers/
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
535 Commits
203 Branches
366 Tags
285 MiB
 
 
 
 
 
 
Tag: Branch: Tree: 836a273544
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '836a273544'
${ noResults }
Go to file
Jon Skeet 836a273544
Create README.md 		10 years ago
build version 2.4.1.555 10 years ago
csproj_templates Collision with known MSBuild property ProjectType was causing errors, renamed to EnvironmentProjectType 13 years ago
keys added batch for creating a new key 14 years ago
lib Build updated NuGet.exe 10 years ago
mono Moved key file to /keys directory 14 years ago
protos Add protoc plugin. 11 years ago
src version 2.4.1.555 10 years ago
testdata line-ending-to-crlf 14 years ago
.gitignore Completion of 3.5 build integration and Lite runtime build changes. 14 years ago
.hgignore Update the Mercurial ignore file for Roslyn. 11 years ago
CHANGES.txt Changes for pulish script 10 years ago
README.md Create README.md 10 years ago
license.txt Fixed line-endings in bat/txt files 14 years ago

README.md

This repo was originally exported from http://code.google.com/p/protobuf-csharp-port, and represents the latest "legacy" version of protobuf-csharp-port.

This project has now been folded into the main Google Protocol Buffers project, and is being revamped to support proto3. It is not expected to be fully backwardly-compatible with the code in this repo - in particular, some of the C#-specific options may not be supported in the new codebase, and some of the generated code may differ. A new major version offers an opportunity to spring-clean, as it were.

This repo exists as an acknowledgement that not everyone will want to immediately use the newer codebase, and that they may wish to make changes to the legacy codebase. I do not expect to make any changes within this repo, but it can be forked for further changes.