Inquiry on Future Compatibility of .NET Framework 4.7.2 with Store Commerce App / dedicated HWS

Discussed in https://github.com/microsoft/Dynamics365Commerce.Solutions/discussions/301

^{Originally posted by cn12xewo June 25, 2024}
Hello,

I am currently working on customizing the standard receipt layout of the Microsoft Store Commerce App to align with specific layout rules and a unique font style, formatted for A5 paper size. For this customization, I have referenced an example from the RetailSDK (HardwareStation.Extension.WindowsPrinterSample.csproj) that is built on .NET Framework 4.6.1.

The current examples for extending the Hardware Station using the Commerce SDK are based on .NET Standard 2.0. In both the Retail SDK example and the current standard (Microsoft.Dynamics.Commerce.HardwareStation.Peripherals.Desktop.dll), System.Drawing is used to render and transmit the information to the Windows printer for printing. However, System.Drawing is not compatible with Commerce SDK and .NET Standard 2.0 as structured in the current examples.

I have successfully migrated the example from the Retail SDK to the Commerce SDK, targeting .NET Framework 4.7.2. This modification works with the current architecture. My concern, however, is regarding the future-proofing of this implementation. Specifically, I would like to know:

How viable is it to continue using .NET Framework 4.7.2 in terms of long-term support and compatibility with future versions of the Store Commerce App and associated hardware stations?
Are there any planned updates or migrations for the Commerce SDK that might affect the functionality of solutions developed on .NET Framework 4.7.2?
I would appreciate any guidance or recommendations on ensuring that our customizations are both effective and sustainable within the Microsoft development ecosystem.

Thank you for your assistance.

Best regards.

Start with HardwareStation.Extension.WindowsPrinterSample.csproj and the RetailSDK example referenced in the issue, then compare them with the Commerce SDK examples and standard Microsoft.Dynamics.Commerce.HardwareStation.Peripherals.Desktop.dll. Review discussion 301 for context; done would be a documented answer about .NET Framework 4.7.2 support and future compatibility.