FluentFTP VS DnsClient.NET

I am using fluent ftp robinrodricks/FluentFTP which is a great library for downloading from ftp sites.

give FluentFTP a try, it's well documented and easy to use.

The PSFTP module is dependent upon System.Net.FtpWebRequest underneath. I believe this has some issues but, unfortunately, is also no longer under any development by MS. I believe they acknowledge there are known bugs for certain scenarios so it may not work but won’t be fixed. I believe that official recommendation is to look for a third-party alternative library! Consider https://github.com/robinrodricks/FluentFTP I believe that is a highly recommended library. Of course this is not a wrapped up PowerShell module like PSFTP, per se, but if you look in the Powershell folder of the git you will find example of usages. Also see here https://github.com/robinrodricks/FluentFTP/issues/434 the library can be used from PowerShell. Likely there are other alternatives too, but fundamentally you probably cannot use the native .Net Framework dependency. I believe newer .Net has superseded all this with entirely different API but that is likely not suitable for your current usage hence the third-party alternative as a recommendation.

Edit: looks like this is supported already https://github.com/robinrodricks/FluentFTP/wiki/File-Transfer so just kill the connection to pause presumably. Call UploadFile or DownLoadFile with existsMode set to append. This will automatically start where it left off.

// in the top of the file // requires installation of https://www.nuget.org/packages/DnsClient using System.Net; using System.Net.Mail; using DnsClient; MailAddress to = new MailAddress("[email protected]"); MailAddress from = new MailAddress("[email protected]"); MailMessage message = new MailMessage(from, to); message.Subject = "See you Monday?"; message.Body = "Elizabeth, I didn't hear back from you. Let me know if we're still scheduled for Monday."; LookupClient lookup = new LookupClient(); IDnsQueryResponse response = lookup.Query("westminster.co.uk", QueryType.MX); foreach(DnsClient.Protocol.MxRecord record in response.Answers) { Console.WriteLine(ObjectDumper.Dump(record.Exchange)); SmtpClient client = new SmtpClient(record.Exchange, 25); try { client.Send(message); // if we reached this point, our email was sent and we can break the loop break; } catch(SmtpException ex) { Console.WriteLine(ex.ToString()); } }

Since there's .NET SDK for MS Teams apps and there's a ready-to-use nuget for DNS it's pretty straightforward for .NET devs who got the time. However, I don't see the real value of such apps when you can just share the link for the queries from sites such as DiG GUI or Dig web interface. If you really want to, you can just create a PowerApps to return the result from those sites without any coding