aboutsummaryrefslogtreecommitdiff
path: root/csharp/src/Google.Protobuf/Google.Protobuf.nuspec
Commit message (Collapse)AuthorAgeFilesLines
* Move to dotnet cli for building, and .NET Core (netstandard1.0) as target ↵Jon Skeet2016-07-141-54/+0
| | | | | | | platform (#1727) Move to dotnet cli for building, and .NET Core (netstandard1.0) as target platform This also updates the version number to 3.0.0-beta4
* Changes to generated code from previous commitJon Skeet2016-07-041-1/+1
|
* Update version numbers for other languagesJisi Liu2016-05-101-2/+2
|
* Use the original name in JSON formatting.Jon Skeet2016-04-201-0/+2
| | | | (JSON parsing already does the right thing.)
* Introduce a new nuget package, Google.Protobuf.Tools, basically to contain ↵Jon Skeet2016-03-311-14/+0
| | | | | | | | protoc on multiple platforms. I've moved both protoc.exe and the proto files out of Google.Protobuf. The .proto files aren't a slam-dunk, but it feels like they belong with protoc as you'd *use* them with protoc. It's not clear to me whether we really need both an x86 and x64 version of protoc.exe, as x86 would work on 64-bit Windows anyway. Discuss :)
* nuspec dependency fixesJon Skeet2016-02-081-0/+10
| | | | | | | Explicitly don't add any dependencies for "old" platforms, to avoid unnecessary dependencies in those cases. Fixes issue #1203.
* make nuget package support CoreCLRJan Tattermusch2015-12-161-19/+38
|
* include descriptor.proto in nuget packageJan Tattermusch2015-08-251-0/+1
|
* make changes and fixes in signingJan Tattermusch2015-08-021-2/+0
|
* added protoc.exe and well known protobuf files to the nuspec fileJan Tattermusch2015-08-021-1/+15
|
* build signed assembliesJan Tattermusch2015-08-021-5/+5
|
* Tweaks to Profile259 supportJon Skeet2015-07-281-4/+4
| | | | | | - Fix nupec paths - Remove an obsolete part of the JSON build - Add documentation and tests to reflection extension methods, and improve implementations
* First pass at the big rename from ProtocolBuffers to Google.Protobuf.Jon Skeet2015-07-171-0/+24
We'll see what I've missed when CI fails...