Module development and the version of .net it uses

[hooligan495]

Question Summary
In using EFLOW (which we know is IOT Edge 1.1) are we constrained to using .net core 3.1 for our modules for now? Or can I spin my own docker file to point to the 5.0 sdks? or if I do that am I asking for more trouble than it's worth?

Detailed background
We are developing some modules and may need some of the SDK support in 5.0. But before I commit to using them I'm wondering if I shouldn't go there. As IOT Edge itself runs on .net core, does it matter how we configure our modules' dockerfiles?
Thanks!

[veyalla]

@hooligan495 Does your module use C# Azure IoT SDK for D2C messages, twin update, direct methods etc?

[hooligan495]

right now we are using the Device SDK (Microsoft.Azure.Devices.Client nuget package)

[veyalla]

While we have not tested this explicitly, I have no reason to believe that it won't work.

I was going to ask you to check in the IoT C# SDK repo to make sure they support .NET 5.0 but saw this blog post today: Azure IoT Hub SDK for .NET now support .NET5 (Preview). :)

Please try it out and open an issue in the IoT C# SDK repo if you run into any problems.