DK for .NET

Documentation | Known issues | DK for .NET

• 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.
• Application should have embedded manifest with uncommented section which typicallly looks like:

    <application xmlns="urn:schemas-microsoft-com:asm.v3">
      <windowsSettings>
        <dpiAware xmlns="http://schemas.microsoft.com/SMI/2005/WindowsSettings">true</dpiAware>
        <longPathAware xmlns="http://schemas.microsoft.com/SMI/2016/WindowsSettings">true</longPathAware>
      </windowsSettings>
    </application>

• Due to restrictions enforced by .NET Framework web services using outdated security are not supported out of the box. If you encounter an error “Could not create SSL/TLS secure channel” or simply some web services do not load, 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. However, compiling an application with .NET 4.6 or newer should resolve the problem as well.

Due to security reasons, TLS lower than 1.2 should be disabled. Starting February 4th, 2020 our tile service works only on TLS 1.2 and/or newer.

• .NET Core (and NET 5.0) Visual Studio WinForms Designer is limited with DK Components (VS 16.8.1). After the download of TatukGIS.DK.NETCore.Windows NuGet package, WPF components instead of on WinForms are presented in a toolbox and therefore can not be added to a form. At this moment the only workaround is to add WinForms component directly in a designer code:

  #region Windows Form Designer generated code
   
  /// <summary>
  ///  Required method for Designer support - do not modify
  ///  the contents of this method with the code editor.
  /// </summary>
  private void InitializeComponent()
  {
    this.GIS = new TatukGIS.NDK.WinForms.TGIS_ViewerWnd(); //### ADD THIS ### 
    this.SuspendLayout();
    // 
    // Form1
    // 
    this.AutoScaleDimensions = new System.Drawing.SizeF(13F, 32F);
    this.AutoScaleMode = System.Windows.Forms.AutoScaleMode.Font;
    this.ClientSize = new System.Drawing.Size(800, 450);
    this.Controls.Add(this.GIS);  //### ADD THIS ###
    this.Name = "Form1";
    this.Text = "Form1";
    this.ResumeLayout(false);
  }
   
  #endregion
   
  private TatukGIS.NDK.WinForms.TGIS_ViewerWnd GIS; //### ADD THIS ###

  Then control will be visible in a designer. Alternatively, just design a form with classic .NET WinForms and port it.
  Microsoft is aware of this issue and status is 'investigating'.