Grpc version download

A way to maintain backwards compatibility while making breaking changes is to publish multiple versions of a service. NET namespace. In fact, the package will be used as the. NET namespace for generated. The package can be used to specify a version number for your service and its messages:. The package name is combined with the service name to identify a service address. A service address allows multiple versions of a service to be hosted side-by-side:.

Including a version number in the package name gives you the opportunity to publish a v2 version of your service with breaking changes, while continuing to support older clients who call the v1 version. Once clients have updated to use the v2 service, you can choose to remove the old version. When planning to publish multiple versions of a service:. Publishing multiple versions of a service duplicates it. To reduce duplication, consider moving business logic from the service implementations to a centralized location that can be reused by the old and new implementations:.

Services and messages generated with different package names are different. Aug 8, Aug 2, Jul 31, Jul 25, Jun 29, Jun 25, Jun 16, Jun 11, Jun 5, May 15, May 4, May 3, Apr 13, Apr 10, Apr 6, Apr 5, Mar 28, Mar 1, Feb 23, Feb 6, Feb 2, Jan 30, Jan 25, Jan 29, Jan 10, Jan 3, Dec 20, Dec 15, Oct 26, Sep 28, May 22, May 17, Apr 28, Mar 29, Mar 20, Feb 24, Jan 31, Dec 14, Dec 10, Oct 12, Aug 19, Aug 11, Jul 20, Jun 28, May 9, Apr 1, Feb 4, Sep 24, Sep 10, Jul 10, May 27, Skip To Content.

Toggle navigation. Core 2. Package Manager. Core -Version 2. Core --version 2. For projects that support PackageReference , copy this XML node into the project file to reference the package.

The NuGet Team does not provide support for this client. Please contact its maintainers for support. Core, 2.