# Logic 2 automation via C# and NET Framework 4.8

**URL:** <https://discuss.saleae.com/t/logic-2-automation-via-c-and-net-framework-4-8/2171>\
**Category:** Support\
**Created:** [March 27, 2023, 4:30pm UTC](https://discuss.saleae.com/t/logic-2-automation-via-c-and-net-framework-4-8/2171 "2023-03-27T16:30:52Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![markgarrison](https://yyz2.discourse-cdn.com/flex030/user_avatar/discuss.saleae.com/markgarrison/32/23_2.png) [@markgarrison](https://discuss.saleae.com/u/markgarrison)\
**Post date:** [March 28, 2023, 8:01pm UTC](https://discuss.saleae.com/t/logic-2-automation-via-c-and-net-framework-4-8/2171/3 "2023-03-28T20:01:10Z")

</div>

@mschreier,

Sorry for the delay with this, and sorry for the trouble!

I’ve finished testing 3 different configurations:

- .NET 7, using Grpc.Net.Client
- .NET framework 4.8, using Grpc.Net.Client and both Grpc.Net.Client.Web and WinHttpHandler
- .NET framework 4.8, using Grpc.Core

I’ve found the same findings as you. There is no way to get .NET Framework 4.8 to work with Grpc.Net.Client, presumably because our application does not support TLS.

NET 7 worked just fine with Grpc.Net.Client, and framework 4.8 worked just fine with Grpc.Core.

Unfortunately, that’s all we can offer at the moment. I recommend you continue to use Grpc.Core even after the maintenance period ends in May.

The only alternative would be for us to add support for TLS, not something that we’re currently planning to add.

---

_[View the full topic](https://discuss.saleae.com/t/logic-2-automation-via-c-and-net-framework-4-8/2171)._