Differences between .NET and COM interfaces

The documentation for the individual classes later in this help file is based on the .NET interface.
The .NET and the COM interfaces are identical except for:

• Connection object constructor
  COM does not support constructor parameters, so the COM version of the Connection object has an additional "Init" method to set the Simple DNS Plus connection parameters.
  When a Connection object is first created, it defaults to a Simple DNS Plus host address 127.0.0.1, port 8053, and a blank password.
  To use different values, use the "Init" method:
  Connection.Init(host, port, {password})

  
• ParamArrays do not pass correctly between .NET and COM
  5 methods in the .NET version uses ParamArrays: DNSRecordCollection.Add, DNSRecordCollection.Contains, DNSRecordCollection.IndexOf, DNSRecordCollection.Remove, and DataFieldCollection.SetAll.
  Therefore the COM version implements these methods both with a number of optional data field parameters, and with an array of data field parameters (method name + "DA"):
  DNSRecordCollection.Add(name, type, data0, {data1},{data2},{data3},{data4},{data5})
DNSRecordCollection.AddDA(name, type, data())
DNSRecordCollection.Contains(name, type, data0, {data1},{data2},{data3},{data4},{data5},{data6})
DNSRecordCollection.ContainsDA(name, type, data())
DNSRecordCollection.IndexOf(name, type, data0, {data1},{data2},{data3},{data4},{data5},{data6})
DNSRecordCollection.IndexOfDA(name, type, data())
DNSRecordCollection.Remove(name, {type}, {data0}, {data1},{data2},{data3},{data4},{data5})
DNSRecordCollection.RemoveDA(name, type, data())
DataFieldCollection.SetAll(data0, {data1},{data2},{data3},{data4},{data5},{data6})
DataFieldCollection.SetAllDA(data())

  
• COM does not support method overloading (multiple versions of same method with different parameters)
  Several methods in the .NET version are overloaded (for example DNSRecordCollection.Remove).
  The COM version uses optional parameters instead, resulting in the same functionality and syntax.
  
  
• IDN domain names in Visual Basic 6
  VB6 applications will only display international characters for the current Windows code page (depends on the language of the installed Windows version, and the Windows Control Panel / Regional and Language options).
  
  
• IDN domain names in classic ASP
  International characters in IDN domain names may not display correctly in classic ASP with the default content-encoding.
  Make sure to set the page encoding to UTF-8.
  In ASP.NET the default encoding is UFT-8 and IDN domains should therefore show correctly without any extra steps.