From 2e8568438b1eff14e19f735eb1c97135dc25a7ee Mon Sep 17 00:00:00 2001 From: Andrew Arnott Date: Mon, 10 Aug 2020 07:24:27 -0600 Subject: [PATCH] Document VS versions for 2.5 and 2.6 --- doc/vs.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/doc/vs.md b/doc/vs.md index 90fb940a..0e48f470 100644 --- a/doc/vs.md +++ b/doc/vs.md @@ -16,6 +16,8 @@ When building a Visual Studio extension, you should not include StreamJsonRpc in | VS 2019.4 | 1.5.x, 2.2.x | VS 2019.5 | 1.5.x, 2.3.x | VS 2019.6 | 1.5.x, 2.4.x +| VS 2019.7 | 1.5.x, 2.5.x +| VS 2019.8 | 1.5.x, 2.6.x StreamJsonRpc versions are forwards and backwards compatible "over the wire". For example it is perfectly legitimate to use StreamJsonRpc 2.4 on the server-side even if the client only uses 1.0, or vice versa. If an RPC method utilizes a newer StreamJsonRpc feature (e.g. `IAsyncEnumerable` return value) and an older client that doesn't support these specially marshaled objects is used to call that method, a memory leak on the server may result.