I'd say stick with what you have if it works. The new ftp classes are subclassed off of the associated web classes...as such I had a booger of a time getting them to work properly in a NAT environment. I don't remember what the exact exception was, but I do remember thinking "of *course* there is a different address than what I originally tried to connect to, isn't that what NAT is all about?" Then I totally abandoned the idea of working with these framework classes in favor of some good ole' C# v1.1 ftp code.
At any rate, most v1.1 ftp implementations used some form of socket programming to get things done, and didn't suffer from this problem. -- -Christopher ASP.NET MVP | AspInsider http://chrisfrazier.net/blog -----Original Message----- From: Discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED] On Behalf Of Franklin Gray Sent: Thursday, July 27, 2006 2:12 PM To: [email protected] Subject: [ADVANCED-DOTNET] New FTP classes Anybody used these yet? I currently have a vb2003 class that handles all of my FTP actions (writing files to server). My boss says I should now use the FTP framework classes. Just wanted to check for issues before I do so. =================================== This list is hosted by DevelopMentor. http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
