DirectFlex only works on Windows processes, which is why it's limited to .exe files. I must admit I've never tried whether we could support .com as well, but given that Windows 10 has less than 10 .com executables, I think that's OK... :-)
.bat and .lnk will eventually reference executables, which you could configure for DirectFlex. What scenarios are you looking at?
Hi Dev, thanks for the fast Response.
Well, in my Case we like to push some App configs only after a user realy Needs it. The User do not only start *.exe files in our envirenment, we have *.bat, *.cmd, *.lnk as well so wie like to Trigger direct Flex with this endings.
1 person found this helpful
But those *.bat, *.cmd, *.lnk files in turn will call *.exe files, right? Can't you just configure those executables for DirectFlex?
Great Dev, thanks again - works totaly fine Seems like the Direct Flex "listen" to the exe wherever this will be started from.
Indeed, we catch any launch of DirectFlex-enabled executables, even if they're not started "directly" by the user.