Generally, it works as expected. However, if you run on the multi-monitor environment when each monitor has a different resolution, the resolution of the main monitor will be used.
On DPI other than standard a rectangle visible upon zooming can be displayed in a completely improper place. A solution is making application DPI aware by enabling in app.manifest section:
<application xmlns="urn:schemas-microsoft-com:asm.v3"> <windowsSettings> <dpiAware xmlns="http://schemas.microsoft.com/SMI/2005/WindowsSettings">true</dpiAware> </windowsSettings> </application>
See also: MSDN Blog.
A real solution will be solved as
DK-9510 in 10.7 final. A small background: We use .NET PointToClient which is buggy. Even the official MS sample for this function does not work on non-standard DPI.
Due to restriction enforced by .NET Framework web services using outdated security are not supported out of the box. If you encounter error “Could not create SSL/TLS secure channel” the default security protocol using ServicePointManager.SecurityProtocol must be changed in the user application:
ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls | SecurityProtocolType.Tls11 | SecurityProtocolType.Tls12 | SecurityProtocolType.Ssl3 ;
This is a .NET Framework restriction.