How come ScreenMaker can be supported while FlexPendant SDK can't?

Rinke

Hello,

I'm currently looking into moving from the FlexPendant SDK to ScreenMaker for making my GUI application that runs on the FlexPendant. From what I understand, the FlexPendant SDK's support is limited because Microsoft isn't supporting the Windows Compact Framework anymore.

What I don't quite understand, though, is why ScreenMaker would be supportable. At the end of the day it still generates .NET code from what I see and then there is the option to add .NET libraries for the "Call .NET Method" option. Doesn't this mean the lack of Windows Compact Framework support also affects ScreenMaker projects?

Can someone explain the difference to me, because I am quite confused on this and don't see how ScreenMaker and optional .NET extensions don't suffer the same issue that prompted ABB to drop FlexPendant SDK support.

I want to have a clearer understanding of this in order to decide how to move forward with my GUI application.

Cheers,
Rinke