Hello all,
as everyone knows, the Ax2012 client Ax32.Exe has a built-in RDP virtual channel extension, to have to possibility to export to an excel application, running on the rdp client, if setup in user options (think this is default)
server = the machine where the ax32 client runs (not neccessary the aos) / the rdp 'server' is meant here
client = export over this virtual channel to the rdp client (which does not need to have something from ax installed, beside the RemoteDesktop Extensions, which installs this virtual channel counterpart on the "RDP client".
The question is the follwoing:
Due to a lot of problems and impossibilities to hold multiple Ax Clients (with a lot of Releases (R1/2/3) and internal builds) on our development machines, we use the RDP based development instead. So we have a lot of developemnt servers with different Ax2012 AOS and client each. (Without an office installed there.)
so far so good.
The question is the following.
Is the VirtualChannel DLL which is installed on the RDP client (there is nothing from Ax there else) from the latest Ax2012Relase (currently it's a R3CU8) downward compatible to all lower virtual channel extensions in the RDP'ed Ax32.Exe's?
It 'seems to work currently', but is this a supported way? Currently we're able to export to excel over this virtual channel independent of the Ax32 client started via RDP. So we can export to our developers excel on the rdp client.
If it isn't?
Is there any chance to install mutliple versions of the VirtualChannel Extension in parallel on the development rdp clients? Means 'registering a lot of these virtual Channel dlls', one from the 2012R1, one from the 2012R2, one from the 2012R3 one from the 2012R3CU8 and so on..
Are there any known changes between the protocoll versions. Maybe newer version support more features ???
regards
Douglas
