Skip to content

Commit 927eaa5

Browse files
committed
docs: tweak some version info
1 parent 4eb2804 commit 927eaa5

File tree

3 files changed

+8
-16
lines changed

3 files changed

+8
-16
lines changed

docs/gettingstarted.md

Lines changed: 4 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22

33
## What is it?
44

5-
> Simple gRPC access in .NET Core 3 - think WCF, but over gRPC
5+
> Simple gRPC access in .NET Core 3+ and .NET Framework 4.6.1+ - think WCF, but over gRPC
66
77
- Google released gRPC, a cross-platform RPC stack over HTTP/2 using protobuf serialization
88
- included in the Google bits is [`Grpc.Core`](https://github.com/grpc/grpc), Google's gRPC bindings for .NET; it has kinks:
@@ -32,18 +32,10 @@ Additionally, it even works with the standard (unmanaged) `Grpc.Core` implementa
3232

3333
### 0: get your build environment
3434

35-
This walkthrough assumes you have the [.NET Core 3 SDK](https://dotnet.microsoft.com/download/dotnet-core/3.0), and an up-to-date compiler, ideally
36-
by having an up-to-date IDE. Note that the tools work on more platforms than just .NET Core 3 (although you'd need to use the unmanaged bindings).
35+
This walkthrough assumes you have the [.NET Core 3.1 SDK or above](https://dotnet.microsoft.com/download/dotnet/current), and an up-to-date compiler, ideally
36+
by having an up-to-date IDE. Note that the tools work on more platforms than just .NET Core (although you'd need to use the unmanaged bindings).
3737

38-
Also: make sure that you are *actually using* the .NET Core 3 SDK, via "global.json"; right now, my "global.json" is:
39-
40-
``` json
41-
{
42-
"sdk": {
43-
"version": "3.0.100"
44-
}
45-
}
46-
```
38+
Also: make sure that you are *actually using* the correct .NET Core SDK (usually via "global.json").
4739

4840
### 1: define your data contracts and service contracts
4941

docs/projects.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -10,8 +10,8 @@ the managed and unmanaged client APIs share a common `ChannelBase` abstraction).
1010

1111
## `protobuf-net.Grpc.AspNetCore`
1212

13-
This is for using gRPC as a **server** with the ASP.NET Core 3 implementation. It takes a dependency on `Grpc.AspNetCore.Server` and `Microsoft.AspNetCore.App`
14-
(although you'll already have the latter if you're hosting in ASP.NET Core). It only works on .NET Core 3 (or above).
13+
This is for using gRPC as a **server** with the ASP.NET Core 3.1 implementation. It takes a dependency on `Grpc.AspNetCore.Server` and `Microsoft.AspNetCore.App`
14+
(although you'll already have the latter if you're hosting in ASP.NET Core). It only works on .NET Core 3.1 (or above).
1515

1616
## `protobuf-net.Grpc.Native`
1717

readme.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -50,9 +50,9 @@ if you prefer: there are [various configuration options](https://protobuf-net.gi
5050

5151
Everything is available as pre-built packages on nuget; in particular, you probably want one of:
5252

53-
- [`protobuf-net.Grpc.AspNetCore`](https://www.nuget.org/packages/protobuf-net.Grpc.AspNetCore) for servers using ASP.NET Core 3
53+
- [`protobuf-net.Grpc.AspNetCore`](https://www.nuget.org/packages/protobuf-net.Grpc.AspNetCore) for servers using ASP.NET Core 3.1
5454
- [`protobuf-net.Grpc.Native`](https://www.nuget.org/packages/protobuf-net.Grpc.Native) for clients or servers using the native/unmanaged API
55-
- [`protobuf-net.Grpc`](https://www.nuget.org/packages/protobuf-net.Grpc) and [`Grpc.Net.Client`](https://www.nuget.org/packages/Grpc.Net.Client/) for clients using `HttpClient` on .NET Core 3
55+
- [`protobuf-net.Grpc`](https://www.nuget.org/packages/protobuf-net.Grpc) and [`Grpc.Net.Client`](https://www.nuget.org/packages/Grpc.Net.Client/) for clients using `HttpClient` on .NET Core 3.1
5656

5757
[Usage examples are available in C#, VB and F#](https://github.com/protobuf-net/protobuf-net.Grpc/tree/main/examples/pb-net-grpc).
5858

0 commit comments

Comments
 (0)