Having an extensive C# development background, as I had mentioned in a previous post, I was thrilled with the ability to access the .NET framework through the dotNET Interoperability introduced with the Microsoft Dynamics NAV Roletailored client.
When interfacing data with other systems it is often necessary to upload files via FTP. It may also be necessary to download files via FTP. This can be accomplished directly in Microsoft Dynamics NAV via Interop.
One of the biggest additions to the development environment with the advent of the RoleTailored Client Microsoft and Dynamics NAV Server was the availability of the Microsoft .NET Framework assemblies. This allows Microsoft Dynamics NAV objects can interact with .NET Framework objects. You can easily use assemblies from the .NET Framework class library, your own custom assemblies; or third-party assemblies. This allows you to extend your solution and not be limited to only the NAV or COM objects.
By using DotNet variables, you can achieve great things, which would otherwise take you a lot of effort / hassle.
Putting a file on an FTP server with C/AL would make you create batch files, specifically a file telling the FTP DOS command where to connect and what to do, without being really sure that the file you put there was actually put on the server…
I have been working on a solution for file download. I am now able to download both binary and text files both via http and ftp and both with Classic Client and Role Tailored Client.