Google.ProtocolBuffers
Protocol Buffers is a binary serialization format and technology, released to the open source community by Google in 2008. Its primary use is to produce small fast binary representations of a 'message' or object for serialization or transportation. There are various implementations of Protocol Buffers in .NET. This project is a fairly close port of the Google Java implementation. There are two main parts: tools/protoc.exe, which takes the textual representation of the protocol buffer and turns it into a binary representation for use with ProtoGen.exe. tools/ProtoGen.exe, which takes binary representations of protocol buffer descriptors (as generated by the "stock" protoc binary supplied by Google) and creates C# source code. This is only required at build time. lib/*/Google.ProtocolBuffers.dll, which is a supporting library. This is required at execution time. lib/*/Google.ProtocolBuffers.Serialization.dll, a supplementary library that provides extensions for reading and writing protocol buffers to xml, json, and others. LINKS: Project Home - http://code.google.com/p/protobuf-csharp-port Online Help - http://help.protobuffers.net Developer Guide - http://code.google.com/apis/protocolbuffers/docs/overview.html Language Guide - http://code.google.com/apis/protocolbuffers/docs/proto.html
Install
dotnet add package Google.ProtocolBuffers --version 2.4.1.555
Install-Package Google.ProtocolBuffers -Version 2.4.1.555
<PackageReference Include="Google.ProtocolBuffers" Version="2.4.1.555" />
Frameworks
No framework metadata available.
Dependencies
No declared dependencies.
Adoption guide
Assess this package against its supported frameworks, license, maintenance signals and dependency graph before making it a project standard.
No SPDX license expression is published. Review the license text and your organisation's policy before redistribution.
No target framework metadata is available. Confirm compatibility in a representative project before standardising on this package.
How to read this guidance
Sources: published NuGet v3 registry metadata and explicit NuBrowse editorial guides. Refresh: package metadata is refreshed from NuGet when the page loads. Limit: this is not a security, legal or compatibility guarantee; validate the selected version in your project.
Useful next steps
Move from package metadata to a concrete selection or review workflow.