ConnectionBar using Remote Desktop Web Connection ActiveX

[Dag]

Using the Remote Desktop Web Connection ActiveX control, I
am trying to configure the Connection bar to "Display"
AND "Auto-hide". Having the Connection bar displayed is
the default behavior, but the Auto-hide option is not.
When the appropriate methods are called they error out.
Is there anyway to enable/configure
the "MsRdpClient.AdvancedSettings2.DisplayConnectionBar"
and "MsRdpClient.AdvancedSettings2.PinConnectionBar"
methods? If no, why not? The "Display Connection bar"
options is configurable in the MSI/EXE version of the RDP
client and should be available AND configurable in the OCX
version as well as. Any input/feedback is appreciated.

Thanks,

Dag

 

[Jeffrey Randow (MVP)]

Have you tried to configure these settings in the default.htm file?
The web client has most of the same methods/properties as the exe
version...

Jeffrey Randow (Windows MVP - Networking & Smart Display)
(e-mail address removed)

Please post all responses to the newsgroups for the benefit
of all USENET users. Messages sent via email may or may not
be answered depending on time availability....

Remote Networking Technology Wiki -
http://www.remotenetworktechnology.com
Smart Display Support - http://www.smartdisplays.net
Windows XP Expert Zone - http://www.microsoft.com/windowsxp/expertzone

 

[Dag]

This is all done in the Default.htm file provided with the
Remote Desktop Web Connection software. When implemented
according to the documentation on the MSDN site
(http://msdn.microsoft.com/library/default.asp?
url=/library/en-
us/termserv/termserv/remote_desktop_activex_control_interfa
ces.asp), the two methods mentioned do not work as
expected (or maybe they do, if they are not meant to work
for security reasons...). If you try it, you'll get
errors processing said methods in IE. I suspect it has
something to do with the special security settings applied
when the control launches in Full Screen mode. I hope
this is something that the can be enabled/disabled by the
user of the product, and not a feature that is
intentionally left disabled/not working because of
potential security concerns....

If it would be possible to find out exactly how this was
intended to work from whoever wrote it, that would be
fantastic.

Regards,

Dag Sjolund