Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(46)

Side by Side Diff: third_party/protobuf/csharp/README.md

Issue 2495533002: third_party/protobuf: Update to HEAD (83d681ee2c) (Closed)
Patch Set: Make chrome settings proto generated file a component Created 4 years ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View unified diff | Download patch
OLDNEW
1 This directory contains the C# Protocol Buffers runtime library. 1 This directory contains the C# Protocol Buffers runtime library.
2 2
3 Status: Beta - ready for external testing
4 =========================================
5
6 Usage 3 Usage
7 ===== 4 =====
8 5
9 The easiest way how to use C# protobufs is via the `Google.Protobuf` 6 The easiest way how to use C# protobufs is via the `Google.Protobuf`
10 NuGet package. Just add the NuGet package to your VS project. 7 NuGet package. Just add the NuGet package to your VS project.
11 8
12 Besides C# runtime library, the NuGet package also contains 9 You will also want to install the `Google.Protobuf.Tools` NuGet package, which
13 precompiled version of `protoc.exe` and a copy of well known `.proto` 10 contains precompiled version of `protoc.exe` and a copy of well known `.proto`
14 files under the package's `tools` directory. 11 files under the package's `tools` directory.
15 12
16 To generate C# files from your `.proto` files, invoke `protoc` with the 13 To generate C# files from your `.proto` files, invoke `protoc` with the
17 `--csharp_out` option. 14 `--csharp_out` option.
18 15
19 Supported platforms 16 Supported platforms
20 =================== 17 ===================
21 18
22 The runtime library is built as a portable class library, supporting: 19 The runtime library is built as a portable class library, supporting:
23 20
(...skipping 37 matching lines...) Expand 10 before | Expand all | Expand 10 after
61 - The old code was based on immutable message types and builders for 58 - The old code was based on immutable message types and builders for
62 them 59 them
63 - The old code did not support maps or `oneof` 60 - The old code did not support maps or `oneof`
64 - The old code had its own JSON representation, whereas the new code 61 - The old code had its own JSON representation, whereas the new code
65 uses the standard protobuf JSON representation 62 uses the standard protobuf JSON representation
66 - The old code had no notion of the "well-known types" which have 63 - The old code had no notion of the "well-known types" which have
67 special support in the new code 64 special support in the new code
68 - The old project supported some older platforms (such as older 65 - The old project supported some older platforms (such as older
69 versions of Silverlight) which are not currently supported in the 66 versions of Silverlight) which are not currently supported in the
70 new project 67 new project
OLDNEW
« no previous file with comments | « third_party/protobuf/csharp/Google.Protobuf.Tools.nuspec ('k') | third_party/protobuf/csharp/build_packages.bat » ('j') | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698