MicrosoftThis is a catastrophic scenario for Devolutions and all of our customers. The built-in RDP ActiveX and mstsc lag behind MSRDC in terms of functionality for regular RDP connections. Things like RDP8.1 dynamic resizing introduced in Windows 8.1 are implemented in MSRDC but not mstsc. We have an integration with MSRDC and the RDP ActiveX it contains (rdclientax.dll) in Remote Desktop Manager, as it was often requested by our customers. Since MSRDC has a faster release cycle, bugs that find their way into mstsc are often "fixed" by switching to MSRDC.
https://blog.devolutions.net/2022/08/extending-the-microsoft-rdp-client-with-api-hooking/
https://blog.devolutions.net/2022/03/msrdc-is-now-supported-in-remote-desktop-manager/
The new Windows App ships a copy of MSRDC, but since it is packaged with an MSIX, we can't access msrdc.exe or rdclientax.dll directly. If Windows App had an MSI installer, we could at least adapt MsRdpEx (https://github.com/Devolutions/MsRdpEx) to load it from there.
I was at the RDP IO Lab in 2023, and discussed this directly with the RDP team: we need an official way to integrate with the out-of-box MSRDC core. Nothing has been done about this, and now you're literally making it impossible to even do an unofficial integration. This will kill the only third-party AVD support from a connection manager in the industry, since mstsc.exe does not support AVD.
Either backtrack on this decision, ship Windows App with an MSI installer, or allow third-party redistribution of MSRDC. We're fine with requiring that MSRDC be separately installed in order to use it, but this means having a package that is installed in a way that we can use the installation files.
