Possible? grpc (client) and grpc-dotnet (server)

Hi together,

we have a .net461 LegacyApp (as a Client) and trying to get a gRPC call to a .netcore Kestrel grpc Server App. For the new one, of course we using dotnet-grpc. (Grpc.AspNetCore nupkg) For the LegacyApp we trying the google core lib(s). (Grpc.Core nupkg)

Looking basicly like that:

Server

public class Program
{
	public static void Main(string[] args)
	{
		CreateHostBuilder(args).Build().Run();
	}

	public static IHostBuilder CreateHostBuilder(string[] args) =>
		Host.CreateDefaultBuilder(args)
			.ConfigureWebHostDefaults(webBuilder =>
			{
                                webBuilder.UseUrls("https://1.2.3.4:3333");
				webBuilder.UseStartup<Startup>();
			});
}

public class Startup
{
	public void ConfigureServices(IServiceCollection services)
	{
		services.AddGrpc();
	}

	public void Configure(IApplicationBuilder app, IWebHostEnvironment env)
	{
		app.UseRouting();
		app.UseEndpoints(endpoints =>
		{
			endpoints.MapGrpcService<MyGrpcService>();
		});
	}
}

Client

	var channel = new Channel("1.2.3.4", 3333, ChannelCredentials.Insecure);
	var client = new MyGrpcServiceClient(channel);

	Console.WriteLine(client.Echo("123"));

Unfortunately, we have not yet managed to get a successful call. When using “google to google” or “grpc-dotnet to grpc-dotnet” all works fine. Is it even possible? If so, what are we doing wrong?

Thank you kl1mm

[JamesNK]

Your ASP.NET Core server is setup with TLS (HTTPS). Your Grpc.Core client is using ChannelCredentials.Insecure which means no TLS. You need to update one of them to match the other.

Any reason why these libraries don’t target .NET Standard 2.0 ?

Features were added in 2.1 (trailers) that are required.

[JamesNK]

They’re the same. SslCredentials.Insecure is inherited from ChannelCredentials.

https://googleapis.github.io/google-cloud-dotnet/docs/Google.Cloud.Diagnostics.AspNet/api/Grpc.Core.SslCredentials.html