<?xml version="1.0"?><?xml-stylesheet type="text/xsl" href="/rss.xsl"?><rss version="2.0"><channel><title>netftp Releases Rss Feed</title><link>http://netftp.codeplex.com/releases</link><description>netftp Releases Rss Description</description><item><title>Updated Release: System.Net.FtpClient 13.5.9.0 (May 09, 2013)</title><link>https://netftp.codeplex.com/releases/view/95632</link><description>&lt;div class="wikidoc"&gt;System.Net.FtpClient is now available via &lt;a href="https://nuget.org/packages/System.Net.FtpClient/"&gt;nuget&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt;This is the first release of the new code base. It is not compatible with the old API, I repeat it is not a drop in update for projects currently using System.Net.FtpClient. New users should download this release. The old code base (Branch: System.Net.FtpClient_1) will continue to be supported while the new code matures. &lt;br /&gt;&lt;br /&gt;This release is a complete re-write of System.Net.FtpClient. The API and code are simpler than ever before. There are some new features included as well as an attempt at better thread safety. Multiple transfers from a single FtpClient object are now supported and async methods are available for nearly every method in FtpClient.&lt;br /&gt;&lt;br /&gt;Support for the FtpFile and FtpDirectory classes have been dropped in favor of the simpler FtpListItem objects. There are no plans to re-introduce these classes in the future.&lt;br /&gt;&lt;br /&gt;Support for the Upload(), Download() and Append() methods has been dropped and there are no plans to re-introduce them. There are however plenty of examples using the OpenRead(), OpenWrite() and OpenAppend() methods.&lt;br /&gt;&lt;br /&gt;The new CHM API reference includes examples for nearly every method in FtpClient including information about debugging and adding custom file listing parsers.&lt;br /&gt;&lt;br /&gt;-- Updates 2012.10.02.01 --&lt;br /&gt;&lt;br /&gt;Binary updated to latest revision, contains several bug fixes for IPv6 and full IPv6 support for control and data connections. Slight API change, EnableIPv6 property removed. If you connect to a IPv6 address everything is handled transparently behind the scenes. If you don&amp;#39;t want use IPv6 consider doing DNS resolution yourself and only connecting to IPv4 addresses.&lt;br /&gt;&lt;br /&gt;-- Updates 2012.10.02.02 --&lt;br /&gt;&lt;br /&gt;1. Fixed problem with GlobalScape&amp;#39;s secure FTP server and data connection SSL authentication.&lt;br /&gt;2. Fixed problem with improper sequencing of PBSZ and PROT commands in regards to requirements outlined by RFC 2228&lt;br /&gt;&lt;br /&gt;-- Updates 12.12.13.0 --&lt;br /&gt;&lt;br /&gt;1. Fixed bugs with thread safe data channels, see commit notes.&lt;br /&gt;2. Fixed bug in SSL validation behavior, you no longer are required to set the Accept property of the event args to True when the SSL certificate is valid.&lt;br /&gt;3. SSL Bug fix in active mode transfers&lt;br /&gt;4. Added support for client ssl certificates though this feature has not been tested or confirmed to be working. That doesn&amp;#39;t mean it doesn&amp;#39;t work, I just don&amp;#39;t have a way to confirm that it indeed does and the person who requested it hasn&amp;#39;t confirmed that it works for them.&lt;br /&gt;&lt;br /&gt;-- Updates 13.01.25.0 --&lt;br /&gt;&lt;br /&gt;1. Added support for NLST using the FtpListOptions.NameList flag. This approach to file listings is the slowest of the bunch however with the proper features on the server side it is the most accurate way to get a file listing with modification times and file size.&lt;br /&gt;2. Fixed bug in MLSD parser where items would fail because the line didn&amp;#39;t begin with ^type=&lt;br /&gt;3. Added check to GetListing() when using LIST where if the modification date is in the future and the MDTM command is supported the server is queried again for the correct modification time. This is feature exists because unix style long listings omit the year in certain situations which can potentially cause a modification time to be off by a year.&lt;br /&gt;4. Added support for parsing VAX/OpenVMS style directory listings. VAX/OpenVMS style paths are not supported however this limitation can be overcome by manually changing to the appropriate directories on the server instead of passing full paths to FtpClient method calls.&lt;br /&gt;5. Fixed bug in CreateDirectory() where 2 attempts to create a directory were made because the path ended with a slash.&lt;br /&gt;&lt;br /&gt;This code should be stable for most if not all people so I&amp;#39;ve changed the download status accordingly. As usual, if you find any bugs please report them or share your fixes. We may not be prompt in getting back to you 100% of the time but we indeed try to address problems in a timely manner.&lt;br /&gt;&lt;br /&gt;-- Updates 13.4.25.0 --&lt;br /&gt;&lt;br /&gt;Lots of changes... here&amp;#39;s a copy and paste from the commit comments:&lt;br /&gt;&lt;br /&gt;1. Added IFtpClient, IFtpListItem and IFtpReply interfaces to assist with MoQ unit testing. No testing has been done.&lt;br /&gt;&lt;br /&gt;2. Fixed bug with restart (REST) sequencing in OpenRead()&lt;br /&gt;&lt;br /&gt;3. More precise server feature matching to avoid false positives.&lt;br /&gt;&lt;br /&gt;4. Bug fix in IIS listing date/time parser.&lt;br /&gt;&lt;br /&gt;5. Reduced socket poll connection test to 500 miliseconds.&lt;br /&gt;&lt;br /&gt;6. MLSD, MDTM and LIST with DOS format (IIS) dates are assumed to be UTC. UNIX and VAX LIST listings are assumed to be local. The basis for this change is that LIST on filezilla gives local date/time values however MDTM and MLSD on filezilla give UTC date/time values. This might become an adjustable property of FtpClient in the future since all servers won&amp;#39;t behave the same in regards to timezones.&lt;br /&gt;&lt;br /&gt;7. Changed date/time parsing code to assume UTC date/time values are being returned from the server. Made modification to Connect() method in effort to detect when there is a disruption immediately upon the initial connection, i.e., before the server greeting can be read. An IOException is thrown when this happens instead of an empty FtpCommandException (what previously happened).&lt;br /&gt; &lt;br /&gt;8. Added code to FtpClient.Execute to detect stale data on the socket, generally due to a timeout + disconnection by the server. The server will sometimes send a disconnection notice that might be sitting in the buffer which breaks the Poll() connectivity test so the data is read and discarded. This still doesn&amp;#39;t guarantee a graceful reconnection, you need to catch IOException&amp;#39;s when you make calls to FtpClient&amp;#39;s method and look for the InnerException to be a SocketException, i.e.,&lt;br /&gt;&lt;br /&gt;try { conn.DoSomething() } catch(IOException e) { if(e.InnerException is SocketException) { // reconnect, DoSomething() again } }&lt;br /&gt;&lt;br /&gt;9. Fixed bug in socket polling code that was used to test for connectivity. Added new SocketPollInterval property (default 15 seconds) that is used to determine how much time should pass since the last read/write before the socket is Poll()&amp;#39;d for connectivity. Polling is used in conjunction with Socket.Connected because Socket.Connected still returns true even when the remote host has closed the connection.&lt;br /&gt;&lt;br /&gt;10. Slight refactoring of FtpSocketStream Connect() method to remove un-necessary exception handling. Added new SocketKeepAlive property that sets SocketOption.KeepAlive accordingly on the underlying stream sockets.&lt;br /&gt;&lt;br /&gt;11. Added support for distribution of System.Net.FtpClient through nuget: https://nuget.org/packages/System.Net.FtpClient/&lt;br /&gt;&lt;br /&gt;-- Updates 13.5.9.0 --&lt;br /&gt;*Added debug output for the total time it takes to negotiate encryption with the server.&lt;br /&gt;*Bug fix with FtpDataConnectionType.AutoActive where the control connection would be closed after the failed EPRT causing a null reference exception while trying to fall back to PORT.&lt;br /&gt;*Added check to avoid null reference exception after failed EPSV command.&lt;br /&gt;*Added check in OpenActiveDataStream to avoid null reference exception after failed EPRT command.&lt;/div&gt;&lt;div class="ClearBoth"&gt;&lt;/div&gt;</description><author>jptrosclair</author><pubDate>Thu, 09 May 2013 15:59:35 GMT</pubDate><guid isPermaLink="false">Updated Release: System.Net.FtpClient 13.5.9.0 (May 09, 2013) 20130509035935P</guid></item><item><title>Released: System.Net.FtpClient 13.5.9.0 (May 09, 2013)</title><link>https://netftp.codeplex.com/releases/view/95632</link><description>
&lt;div class="wikidoc"&gt;System.Net.FtpClient is now available via &lt;a href="https://nuget.org/packages/System.Net.FtpClient/"&gt;
nuget&lt;/a&gt;.&lt;br&gt;
&lt;br&gt;
This is the first release of the new code base. It is not compatible with the old API, I repeat it is not a drop in update for projects currently using System.Net.FtpClient. New users should download this release. The old code base (Branch: System.Net.FtpClient_1)
 will continue to be supported while the new code matures. &lt;br&gt;
&lt;br&gt;
This release is a complete re-write of System.Net.FtpClient. The API and code are simpler than ever before. There are some new features included as well as an attempt at better thread safety. Multiple transfers from a single FtpClient object are now supported
 and async methods are available for nearly every method in FtpClient.&lt;br&gt;
&lt;br&gt;
Support for the FtpFile and FtpDirectory classes have been dropped in favor of the simpler FtpListItem objects. There are no plans to re-introduce these classes in the future.&lt;br&gt;
&lt;br&gt;
Support for the Upload(), Download() and Append() methods has been dropped and there are no plans to re-introduce them. There are however plenty of examples using the OpenRead(), OpenWrite() and OpenAppend() methods.&lt;br&gt;
&lt;br&gt;
The new CHM API reference includes examples for nearly every method in FtpClient including information about debugging and adding custom file listing parsers.&lt;br&gt;
&lt;br&gt;
-- Updates 2012.10.02.01 --&lt;br&gt;
&lt;br&gt;
Binary updated to latest revision, contains several bug fixes for IPv6 and full IPv6 support for control and data connections. Slight API change, EnableIPv6 property removed. If you connect to a IPv6 address everything is handled transparently behind the scenes.
 If you don&amp;#39;t want use IPv6 consider doing DNS resolution yourself and only connecting to IPv4 addresses.&lt;br&gt;
&lt;br&gt;
-- Updates 2012.10.02.02 --&lt;br&gt;
&lt;br&gt;
1. Fixed problem with GlobalScape&amp;#39;s secure FTP server and data connection SSL authentication.&lt;br&gt;
2. Fixed problem with improper sequencing of PBSZ and PROT commands in regards to requirements outlined by RFC 2228&lt;br&gt;
&lt;br&gt;
-- Updates 12.12.13.0 --&lt;br&gt;
&lt;br&gt;
1. Fixed bugs with thread safe data channels, see commit notes.&lt;br&gt;
2. Fixed bug in SSL validation behavior, you no longer are required to set the Accept property of the event args to True when the SSL certificate is valid.&lt;br&gt;
3. SSL Bug fix in active mode transfers&lt;br&gt;
4. Added support for client ssl certificates though this feature has not been tested or confirmed to be working. That doesn&amp;#39;t mean it doesn&amp;#39;t work, I just don&amp;#39;t have a way to confirm that it indeed does and the person who requested it hasn&amp;#39;t
 confirmed that it works for them.&lt;br&gt;
&lt;br&gt;
-- Updates 13.01.25.0 --&lt;br&gt;
&lt;br&gt;
1. Added support for NLST using the FtpListOptions.NameList flag. This approach to file listings is the slowest of the bunch however with the proper features on the server side it is the most accurate way to get a file listing with modification times and file
 size.&lt;br&gt;
2. Fixed bug in MLSD parser where items would fail because the line didn&amp;#39;t begin with ^type=&lt;br&gt;
3. Added check to GetListing() when using LIST where if the modification date is in the future and the MDTM command is supported the server is queried again for the correct modification time. This is feature exists because unix style long listings omit the
 year in certain situations which can potentially cause a modification time to be off by a year.&lt;br&gt;
4. Added support for parsing VAX/OpenVMS style directory listings. VAX/OpenVMS style paths are not supported however this limitation can be overcome by manually changing to the appropriate directories on the server instead of passing full paths to FtpClient
 method calls.&lt;br&gt;
5. Fixed bug in CreateDirectory() where 2 attempts to create a directory were made because the path ended with a slash.&lt;br&gt;
&lt;br&gt;
This code should be stable for most if not all people so I&amp;#39;ve changed the download status accordingly. As usual, if you find any bugs please report them or share your fixes. We may not be prompt in getting back to you 100% of the time but we indeed try
 to address problems in a timely manner.&lt;br&gt;
&lt;br&gt;
-- Updates 13.4.25.0 --&lt;br&gt;
&lt;br&gt;
Lots of changes... here&amp;#39;s a copy and paste from the commit comments:&lt;br&gt;
&lt;br&gt;
1. Added IFtpClient, IFtpListItem and IFtpReply interfaces to assist with MoQ unit testing. No testing has been done.&lt;br&gt;
&lt;br&gt;
2. Fixed bug with restart (REST) sequencing in OpenRead()&lt;br&gt;
&lt;br&gt;
3. More precise server feature matching to avoid false positives.&lt;br&gt;
&lt;br&gt;
4. Bug fix in IIS listing date/time parser.&lt;br&gt;
&lt;br&gt;
5. Reduced socket poll connection test to 500 miliseconds.&lt;br&gt;
&lt;br&gt;
6. MLSD, MDTM and LIST with DOS format (IIS) dates are assumed to be UTC. UNIX and VAX LIST listings are assumed to be local. The basis for this change is that LIST on filezilla gives local date/time values however MDTM and MLSD on filezilla give UTC date/time
 values. This might become an adjustable property of FtpClient in the future since all servers won&amp;#39;t behave the same in regards to timezones.&lt;br&gt;
&lt;br&gt;
7. Changed date/time parsing code to assume UTC date/time values are being returned from the server. Made modification to Connect() method in effort to detect when there is a disruption immediately upon the initial connection, i.e., before the server greeting
 can be read. An IOException is thrown when this happens instead of an empty FtpCommandException (what previously happened).&lt;br&gt;
&lt;br&gt;
8. Added code to FtpClient.Execute to detect stale data on the socket, generally due to a timeout &amp;#43; disconnection by the server. The server will sometimes send a disconnection notice that might be sitting in the buffer which breaks the Poll() connectivity test
 so the data is read and discarded. This still doesn&amp;#39;t guarantee a graceful reconnection, you need to catch IOException&amp;#39;s when you make calls to FtpClient&amp;#39;s method and look for the InnerException to be a SocketException, i.e.,&lt;br&gt;
&lt;br&gt;
try { conn.DoSomething() } catch(IOException e) { if(e.InnerException is SocketException) { // reconnect, DoSomething() again } }&lt;br&gt;
&lt;br&gt;
9. Fixed bug in socket polling code that was used to test for connectivity. Added new SocketPollInterval property (default 15 seconds) that is used to determine how much time should pass since the last read/write before the socket is Poll()&amp;#39;d for connectivity.
 Polling is used in conjunction with Socket.Connected because Socket.Connected still returns true even when the remote host has closed the connection.&lt;br&gt;
&lt;br&gt;
10. Slight refactoring of FtpSocketStream Connect() method to remove un-necessary exception handling. Added new SocketKeepAlive property that sets SocketOption.KeepAlive accordingly on the underlying stream sockets.&lt;br&gt;
&lt;br&gt;
11. Added support for distribution of System.Net.FtpClient through nuget: https://nuget.org/packages/System.Net.FtpClient/&lt;br&gt;
&lt;br&gt;
-- Updates 13.5.9.0 --&lt;br&gt;
*Added debug output for the total time it takes to negotiate encryption with the server.&lt;br&gt;
*Bug fix with FtpDataConnectionType.AutoActive where the control connection would be closed after the failed EPRT causing a null reference exception while trying to fall back to PORT.&lt;br&gt;
*Added check to avoid null reference exception after failed EPSV command.&lt;br&gt;
*Added check in OpenActiveDataStream to avoid null reference exception after failed EPRT command.&lt;/div&gt;
&lt;div&gt;&lt;/div&gt;
</description><author></author><pubDate>Thu, 09 May 2013 15:59:35 GMT</pubDate><guid isPermaLink="false">Released: System.Net.FtpClient 13.5.9.0 (May 09, 2013) 20130509035935P</guid></item><item><title>Updated Release: System.Net.FtpClient 13.4.25.0 (Apr 25, 2013)</title><link>https://netftp.codeplex.com/releases/view/95632</link><description>&lt;div class="wikidoc"&gt;System.Net.FtpClient is now available via &lt;a href="https://nuget.org/packages/System.Net.FtpClient/"&gt;nuget&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt;This is the first release of the new code base. It is not compatible with the old API, I repeat it is not a drop in update for projects currently using System.Net.FtpClient. New users should download this release. The old code base (Branch: System.Net.FtpClient_1) will continue to be supported while the new code matures. &lt;br /&gt;&lt;br /&gt;This release is a complete re-write of System.Net.FtpClient. The API and code are simpler than ever before. There are some new features included as well as an attempt at better thread safety. Multiple transfers from a single FtpClient object are now supported and async methods are available for nearly every method in FtpClient.&lt;br /&gt;&lt;br /&gt;Support for the FtpFile and FtpDirectory classes have been dropped in favor of the simpler FtpListItem objects. There are no plans to re-introduce these classes in the future.&lt;br /&gt;&lt;br /&gt;Support for the Upload(), Download() and Append() methods has been dropped and there are no plans to re-introduce them. There are however plenty of examples using the OpenRead(), OpenWrite() and OpenAppend() methods.&lt;br /&gt;&lt;br /&gt;The new CHM API reference includes examples for nearly every method in FtpClient including information about debugging and adding custom file listing parsers.&lt;br /&gt;&lt;br /&gt;-- Updates 2012.10.02.01 --&lt;br /&gt;&lt;br /&gt;Binary updated to latest revision, contains several bug fixes for IPv6 and full IPv6 support for control and data connections. Slight API change, EnableIPv6 property removed. If you connect to a IPv6 address everything is handled transparently behind the scenes. If you don&amp;#39;t want use IPv6 consider doing DNS resolution yourself and only connecting to IPv4 addresses.&lt;br /&gt;&lt;br /&gt;-- Updates 2012.10.02.02 --&lt;br /&gt;&lt;br /&gt;1. Fixed problem with GlobalScape&amp;#39;s secure FTP server and data connection SSL authentication.&lt;br /&gt;2. Fixed problem with improper sequencing of PBSZ and PROT commands in regards to requirements outlined by RFC 2228&lt;br /&gt;&lt;br /&gt;-- Updates 12.12.13.0 --&lt;br /&gt;&lt;br /&gt;1. Fixed bugs with thread safe data channels, see commit notes.&lt;br /&gt;2. Fixed bug in SSL validation behavior, you no longer are required to set the Accept property of the event args to True when the SSL certificate is valid.&lt;br /&gt;3. SSL Bug fix in active mode transfers&lt;br /&gt;4. Added support for client ssl certificates though this feature has not been tested or confirmed to be working. That doesn&amp;#39;t mean it doesn&amp;#39;t work, I just don&amp;#39;t have a way to confirm that it indeed does and the person who requested it hasn&amp;#39;t confirmed that it works for them.&lt;br /&gt;&lt;br /&gt;-- Updates 13.01.25.0 --&lt;br /&gt;&lt;br /&gt;1. Added support for NLST using the FtpListOptions.NameList flag. This approach to file listings is the slowest of the bunch however with the proper features on the server side it is the most accurate way to get a file listing with modification times and file size.&lt;br /&gt;2. Fixed bug in MLSD parser where items would fail because the line didn&amp;#39;t begin with ^type=&lt;br /&gt;3. Added check to GetListing() when using LIST where if the modification date is in the future and the MDTM command is supported the server is queried again for the correct modification time. This is feature exists because unix style long listings omit the year in certain situations which can potentially cause a modification time to be off by a year.&lt;br /&gt;4. Added support for parsing VAX/OpenVMS style directory listings. VAX/OpenVMS style paths are not supported however this limitation can be overcome by manually changing to the appropriate directories on the server instead of passing full paths to FtpClient method calls.&lt;br /&gt;5. Fixed bug in CreateDirectory() where 2 attempts to create a directory were made because the path ended with a slash.&lt;br /&gt;&lt;br /&gt;This code should be stable for most if not all people so I&amp;#39;ve changed the download status accordingly. As usual, if you find any bugs please report them or share your fixes. We may not be prompt in getting back to you 100% of the time but we indeed try to address problems in a timely manner.&lt;br /&gt;&lt;br /&gt;-- Updates 13.4.25.0 --&lt;br /&gt;&lt;br /&gt;Lots of changes... here&amp;#39;s a copy and paste from the commit comments:&lt;br /&gt;&lt;br /&gt;1. Added IFtpClient, IFtpListItem and IFtpReply interfaces to assist with MoQ unit testing. No testing has been done.&lt;br /&gt;&lt;br /&gt;2. Fixed bug with restart (REST) sequencing in OpenRead()&lt;br /&gt;&lt;br /&gt;3. More precise server feature matching to avoid false positives.&lt;br /&gt;&lt;br /&gt;4. Bug fix in IIS listing date/time parser.&lt;br /&gt;&lt;br /&gt;5. Reduced socket poll connection test to 500 miliseconds.&lt;br /&gt;&lt;br /&gt;6. MLSD, MDTM and LIST with DOS format (IIS) dates are assumed to be UTC. UNIX and VAX LIST listings are assumed to be local. The basis for this change is that LIST on filezilla gives local date/time values however MDTM and MLSD on filezilla give UTC date/time values. This might become an adjustable property of FtpClient in the future since all servers won&amp;#39;t behave the same in regards to timezones.&lt;br /&gt;&lt;br /&gt;7. Changed date/time parsing code to assume UTC date/time values are being returned from the server. Made modification to Connect() method in effort to detect when there is a disruption immediately upon the initial connection, i.e., before the server greeting can be read. An IOException is thrown when this happens instead of an empty FtpCommandException (what previously happened).&lt;br /&gt; &lt;br /&gt;8. Added code to FtpClient.Execute to detect stale data on the socket, generally due to a timeout + disconnection by the server. The server will sometimes send a disconnection notice that might be sitting in the buffer which breaks the Poll() connectivity test so the data is read and discarded. This still doesn&amp;#39;t guarantee a graceful reconnection, you need to catch IOException&amp;#39;s when you make calls to FtpClient&amp;#39;s method and look for the InnerException to be a SocketException, i.e.,&lt;br /&gt;&lt;br /&gt;try { conn.DoSomething() } catch(IOException e) { if(e.InnerException is SocketException) { // reconnect, DoSomething() again } }&lt;br /&gt;&lt;br /&gt;9. Fixed bug in socket polling code that was used to test for connectivity. Added new SocketPollInterval property (default 15 seconds) that is used to determine how much time should pass since the last read/write before the socket is Poll()&amp;#39;d for connectivity. Polling is used in conjunction with Socket.Connected because Socket.Connected still returns true even when the remote host has closed the connection.&lt;br /&gt;&lt;br /&gt;10. Slight refactoring of FtpSocketStream Connect() method to remove un-necessary exception handling. Added new SocketKeepAlive property that sets SocketOption.KeepAlive accordingly on the underlying stream sockets.&lt;br /&gt;&lt;br /&gt;11. Added support for distribution of System.Net.FtpClient through nuget: https://nuget.org/packages/System.Net.FtpClient/&lt;/div&gt;&lt;div class="ClearBoth"&gt;&lt;/div&gt;</description><author>jptrosclair</author><pubDate>Thu, 25 Apr 2013 17:40:19 GMT</pubDate><guid isPermaLink="false">Updated Release: System.Net.FtpClient 13.4.25.0 (Apr 25, 2013) 20130425054019P</guid></item><item><title>Released: System.Net.FtpClient 13.4.25.0 (Apr 25, 2013)</title><link>http://netftp.codeplex.com/releases/view/95632</link><description>
&lt;div class="wikidoc"&gt;System.Net.FtpClient is now available via &lt;a href="https://nuget.org/packages/System.Net.FtpClient/"&gt;
nuget&lt;/a&gt;.&lt;br&gt;
&lt;br&gt;
This is the first release of the new code base. It is not compatible with the old API, I repeat it is not a drop in update for projects currently using System.Net.FtpClient. New users should download this release. The old code base (Branch: System.Net.FtpClient_1)
 will continue to be supported while the new code matures. &lt;br&gt;
&lt;br&gt;
This release is a complete re-write of System.Net.FtpClient. The API and code are simpler than ever before. There are some new features included as well as an attempt at better thread safety. Multiple transfers from a single FtpClient object are now supported
 and async methods are available for nearly every method in FtpClient.&lt;br&gt;
&lt;br&gt;
Support for the FtpFile and FtpDirectory classes have been dropped in favor of the simpler FtpListItem objects. There are no plans to re-introduce these classes in the future.&lt;br&gt;
&lt;br&gt;
Support for the Upload(), Download() and Append() methods has been dropped and there are no plans to re-introduce them. There are however plenty of examples using the OpenRead(), OpenWrite() and OpenAppend() methods.&lt;br&gt;
&lt;br&gt;
The new CHM API reference includes examples for nearly every method in FtpClient including information about debugging and adding custom file listing parsers.&lt;br&gt;
&lt;br&gt;
-- Updates 2012.10.02.01 --&lt;br&gt;
&lt;br&gt;
Binary updated to latest revision, contains several bug fixes for IPv6 and full IPv6 support for control and data connections. Slight API change, EnableIPv6 property removed. If you connect to a IPv6 address everything is handled transparently behind the scenes.
 If you don&amp;#39;t want use IPv6 consider doing DNS resolution yourself and only connecting to IPv4 addresses.&lt;br&gt;
&lt;br&gt;
-- Updates 2012.10.02.02 --&lt;br&gt;
&lt;br&gt;
1. Fixed problem with GlobalScape&amp;#39;s secure FTP server and data connection SSL authentication.&lt;br&gt;
2. Fixed problem with improper sequencing of PBSZ and PROT commands in regards to requirements outlined by RFC 2228&lt;br&gt;
&lt;br&gt;
-- Updates 12.12.13.0 --&lt;br&gt;
&lt;br&gt;
1. Fixed bugs with thread safe data channels, see commit notes.&lt;br&gt;
2. Fixed bug in SSL validation behavior, you no longer are required to set the Accept property of the event args to True when the SSL certificate is valid.&lt;br&gt;
3. SSL Bug fix in active mode transfers&lt;br&gt;
4. Added support for client ssl certificates though this feature has not been tested or confirmed to be working. That doesn&amp;#39;t mean it doesn&amp;#39;t work, I just don&amp;#39;t have a way to confirm that it indeed does and the person who requested it hasn&amp;#39;t
 confirmed that it works for them.&lt;br&gt;
&lt;br&gt;
-- Updates 13.01.25.0 --&lt;br&gt;
&lt;br&gt;
1. Added support for NLST using the FtpListOptions.NameList flag. This approach to file listings is the slowest of the bunch however with the proper features on the server side it is the most accurate way to get a file listing with modification times and file
 size.&lt;br&gt;
2. Fixed bug in MLSD parser where items would fail because the line didn&amp;#39;t begin with ^type=&lt;br&gt;
3. Added check to GetListing() when using LIST where if the modification date is in the future and the MDTM command is supported the server is queried again for the correct modification time. This is feature exists because unix style long listings omit the
 year in certain situations which can potentially cause a modification time to be off by a year.&lt;br&gt;
4. Added support for parsing VAX/OpenVMS style directory listings. VAX/OpenVMS style paths are not supported however this limitation can be overcome by manually changing to the appropriate directories on the server instead of passing full paths to FtpClient
 method calls.&lt;br&gt;
5. Fixed bug in CreateDirectory() where 2 attempts to create a directory were made because the path ended with a slash.&lt;br&gt;
&lt;br&gt;
This code should be stable for most if not all people so I&amp;#39;ve changed the download status accordingly. As usual, if you find any bugs please report them or share your fixes. We may not be prompt in getting back to you 100% of the time but we indeed try
 to address problems in a timely manner.&lt;br&gt;
&lt;br&gt;
-- Updates 13.4.25.0 --&lt;br&gt;
&lt;br&gt;
Lots of changes... here&amp;#39;s a copy and paste from the commit comments:&lt;br&gt;
&lt;br&gt;
1. Added IFtpClient, IFtpListItem and IFtpReply interfaces to assist with MoQ unit testing. No testing has been done.&lt;br&gt;
&lt;br&gt;
2. Fixed bug with restart (REST) sequencing in OpenRead()&lt;br&gt;
&lt;br&gt;
3. More precise server feature matching to avoid false positives.&lt;br&gt;
&lt;br&gt;
4. Bug fix in IIS listing date/time parser.&lt;br&gt;
&lt;br&gt;
5. Reduced socket poll connection test to 500 miliseconds.&lt;br&gt;
&lt;br&gt;
6. MLSD, MDTM and LIST with DOS format (IIS) dates are assumed to be UTC. UNIX and VAX LIST listings are assumed to be local. The basis for this change is that LIST on filezilla gives local date/time values however MDTM and MLSD on filezilla give UTC date/time
 values. This might become an adjustable property of FtpClient in the future since all servers won&amp;#39;t behave the same in regards to timezones.&lt;br&gt;
&lt;br&gt;
7. Changed date/time parsing code to assume UTC date/time values are being returned from the server. Made modification to Connect() method in effort to detect when there is a disruption immediately upon the initial connection, i.e., before the server greeting
 can be read. An IOException is thrown when this happens instead of an empty FtpCommandException (what previously happened).&lt;br&gt;
&lt;br&gt;
8. Added code to FtpClient.Execute to detect stale data on the socket, generally due to a timeout &amp;#43; disconnection by the server. The server will sometimes send a disconnection notice that might be sitting in the buffer which breaks the Poll() connectivity test
 so the data is read and discarded. This still doesn&amp;#39;t guarantee a graceful reconnection, you need to catch IOException&amp;#39;s when you make calls to FtpClient&amp;#39;s method and look for the InnerException to be a SocketException, i.e.,&lt;br&gt;
&lt;br&gt;
try { conn.DoSomething() } catch(IOException e) { if(e.InnerException is SocketException) { // reconnect, DoSomething() again } }&lt;br&gt;
&lt;br&gt;
9. Fixed bug in socket polling code that was used to test for connectivity. Added new SocketPollInterval property (default 15 seconds) that is used to determine how much time should pass since the last read/write before the socket is Poll()&amp;#39;d for connectivity.
 Polling is used in conjunction with Socket.Connected because Socket.Connected still returns true even when the remote host has closed the connection.&lt;br&gt;
&lt;br&gt;
10. Slight refactoring of FtpSocketStream Connect() method to remove un-necessary exception handling. Added new SocketKeepAlive property that sets SocketOption.KeepAlive accordingly on the underlying stream sockets.&lt;br&gt;
&lt;br&gt;
11. Added support for distribution of System.Net.FtpClient through nuget: https://nuget.org/packages/System.Net.FtpClient/&lt;/div&gt;
&lt;div&gt;&lt;/div&gt;
</description><author></author><pubDate>Thu, 25 Apr 2013 17:40:19 GMT</pubDate><guid isPermaLink="false">Released: System.Net.FtpClient 13.4.25.0 (Apr 25, 2013) 20130425054019P</guid></item><item><title>Updated Release: System.Net.FtpClient 13.4.25.0 (Apr 25, 2013)</title><link>https://netftp.codeplex.com/releases/view/95632</link><description>&lt;div class="wikidoc"&gt;This is the first release of the new code base. It is not compatible with the old API, I repeat it is not a drop in update for projects currently using System.Net.FtpClient. New users should download this release. The old code base (Branch: System.Net.FtpClient_1) will continue to be supported while the new code matures. &lt;br /&gt;&lt;br /&gt;This release is a complete re-write of System.Net.FtpClient. The API and code are simpler than ever before. There are some new features included as well as an attempt at better thread safety. Multiple transfers from a single FtpClient object are now supported and async methods are available for nearly every method in FtpClient.&lt;br /&gt;&lt;br /&gt;Support for the FtpFile and FtpDirectory classes have been dropped in favor of the simpler FtpListItem objects. There are no plans to re-introduce these classes in the future.&lt;br /&gt;&lt;br /&gt;Support for the Upload(), Download() and Append() methods has been dropped and there are no plans to re-introduce them. There are however plenty of examples using the OpenRead(), OpenWrite() and OpenAppend() methods.&lt;br /&gt;&lt;br /&gt;The new CHM API reference includes examples for nearly every method in FtpClient including information about debugging and adding custom file listing parsers.&lt;br /&gt;&lt;br /&gt;-- Updates 2012.10.02.01 --&lt;br /&gt;&lt;br /&gt;Binary updated to latest revision, contains several bug fixes for IPv6 and full IPv6 support for control and data connections. Slight API change, EnableIPv6 property removed. If you connect to a IPv6 address everything is handled transparently behind the scenes. If you don&amp;#39;t want use IPv6 consider doing DNS resolution yourself and only connecting to IPv4 addresses.&lt;br /&gt;&lt;br /&gt;-- Updates 2012.10.02.02 --&lt;br /&gt;&lt;br /&gt;1. Fixed problem with GlobalScape&amp;#39;s secure FTP server and data connection SSL authentication.&lt;br /&gt;2. Fixed problem with improper sequencing of PBSZ and PROT commands in regards to requirements outlined by RFC 2228&lt;br /&gt;&lt;br /&gt;-- Updates 12.12.13.0 --&lt;br /&gt;&lt;br /&gt;1. Fixed bugs with thread safe data channels, see commit notes.&lt;br /&gt;2. Fixed bug in SSL validation behavior, you no longer are required to set the Accept property of the event args to True when the SSL certificate is valid.&lt;br /&gt;3. SSL Bug fix in active mode transfers&lt;br /&gt;4. Added support for client ssl certificates though this feature has not been tested or confirmed to be working. That doesn&amp;#39;t mean it doesn&amp;#39;t work, I just don&amp;#39;t have a way to confirm that it indeed does and the person who requested it hasn&amp;#39;t confirmed that it works for them.&lt;br /&gt;&lt;br /&gt;-- Updates 13.01.25.0 --&lt;br /&gt;&lt;br /&gt;1. Added support for NLST using the FtpListOptions.NameList flag. This approach to file listings is the slowest of the bunch however with the proper features on the server side it is the most accurate way to get a file listing with modification times and file size.&lt;br /&gt;2. Fixed bug in MLSD parser where items would fail because the line didn&amp;#39;t begin with ^type=&lt;br /&gt;3. Added check to GetListing() when using LIST where if the modification date is in the future and the MDTM command is supported the server is queried again for the correct modification time. This is feature exists because unix style long listings omit the year in certain situations which can potentially cause a modification time to be off by a year.&lt;br /&gt;4. Added support for parsing VAX/OpenVMS style directory listings. VAX/OpenVMS style paths are not supported however this limitation can be overcome by manually changing to the appropriate directories on the server instead of passing full paths to FtpClient method calls.&lt;br /&gt;5. Fixed bug in CreateDirectory() where 2 attempts to create a directory were made because the path ended with a slash.&lt;br /&gt;&lt;br /&gt;This code should be stable for most if not all people so I&amp;#39;ve changed the download status accordingly. As usual, if you find any bugs please report them or share your fixes. We may not be prompt in getting back to you 100% of the time but we indeed try to address problems in a timely manner.&lt;br /&gt;&lt;br /&gt;-- Updates 13.4.25.0 --&lt;br /&gt;&lt;br /&gt;Lots of changes... here&amp;#39;s a copy and paste from the commit comments:&lt;br /&gt;&lt;br /&gt;1. Added IFtpClient, IFtpListItem and IFtpReply interfaces to assist with MoQ unit testing. No testing has been done.&lt;br /&gt;&lt;br /&gt;2. Fixed bug with restart (REST) sequencing in OpenRead()&lt;br /&gt;&lt;br /&gt;3. More precise server feature matching to avoid false positives.&lt;br /&gt;&lt;br /&gt;4. Bug fix in IIS listing date/time parser.&lt;br /&gt;&lt;br /&gt;5. Reduced socket poll connection test to 500 miliseconds.&lt;br /&gt;&lt;br /&gt;6. MLSD, MDTM and LIST with DOS format (IIS) dates are assumed to be UTC. UNIX and VAX LIST listings are assumed to be local. The basis for this change is that LIST on filezilla gives local date/time values however MDTM and MLSD on filezilla give UTC date/time values. This might become an adjustable property of FtpClient in the future since all servers won&amp;#39;t behave the same in regards to timezones.&lt;br /&gt;&lt;br /&gt;7. Changed date/time parsing code to assume UTC date/time values are being returned from the server. Made modification to Connect() method in effort to detect when there is a disruption immediately upon the initial connection, i.e., before the server greeting can be read. An IOException is thrown when this happens instead of an empty FtpCommandException (what previously happened).&lt;br /&gt; &lt;br /&gt;8. Added code to FtpClient.Execute to detect stale data on the socket, generally due to a timeout + disconnection by the server. The server will sometimes send a disconnection notice that might be sitting in the buffer which breaks the Poll() connectivity test so the data is read and discarded. This still doesn&amp;#39;t guarantee a graceful reconnection, you need to catch IOException&amp;#39;s when you make calls to FtpClient&amp;#39;s method and look for the InnerException to be a SocketException, i.e.,&lt;br /&gt;&lt;br /&gt;try { conn.DoSomething() } catch(IOException e) { if(e.InnerException is SocketException) { // reconnect, DoSomething() again } }&lt;br /&gt;&lt;br /&gt;9. Fixed bug in socket polling code that was used to test for connectivity. Added new SocketPollInterval property (default 15 seconds) that is used to determine how much time should pass since the last read/write before the socket is Poll()&amp;#39;d for connectivity. Polling is used in conjunction with Socket.Connected because Socket.Connected still returns true even when the remote host has closed the connection.&lt;br /&gt;&lt;br /&gt;10. Slight refactoring of FtpSocketStream Connect() method to remove un-necessary exception handling. Added new SocketKeepAlive property that sets SocketOption.KeepAlive accordingly on the underlying stream sockets.&lt;br /&gt;&lt;br /&gt;11. Added support for distribution of System.Net.FtpClient through nuget: https://nuget.org/packages/System.Net.FtpClient/&lt;/div&gt;&lt;div class="ClearBoth"&gt;&lt;/div&gt;</description><author>jptrosclair</author><pubDate>Thu, 25 Apr 2013 15:34:55 GMT</pubDate><guid isPermaLink="false">Updated Release: System.Net.FtpClient 13.4.25.0 (Apr 25, 2013) 20130425033455P</guid></item><item><title>Released: System.Net.FtpClient 13.4.25.0 (Apr 25, 2013)</title><link>https://netftp.codeplex.com/releases/view/95632</link><description>
&lt;div class="wikidoc"&gt;This is the first release of the new code base. It is not compatible with the old API, I repeat it is not a drop in update for projects currently using System.Net.FtpClient. New users should download this release. The old code base (Branch:
 System.Net.FtpClient_1) will continue to be supported while the new code matures.
&lt;br&gt;
&lt;br&gt;
This release is a complete re-write of System.Net.FtpClient. The API and code are simpler than ever before. There are some new features included as well as an attempt at better thread safety. Multiple transfers from a single FtpClient object are now supported
 and async methods are available for nearly every method in FtpClient.&lt;br&gt;
&lt;br&gt;
Support for the FtpFile and FtpDirectory classes have been dropped in favor of the simpler FtpListItem objects. There are no plans to re-introduce these classes in the future.&lt;br&gt;
&lt;br&gt;
Support for the Upload(), Download() and Append() methods has been dropped and there are no plans to re-introduce them. There are however plenty of examples using the OpenRead(), OpenWrite() and OpenAppend() methods.&lt;br&gt;
&lt;br&gt;
The new CHM API reference includes examples for nearly every method in FtpClient including information about debugging and adding custom file listing parsers.&lt;br&gt;
&lt;br&gt;
-- Updates 2012.10.02.01 --&lt;br&gt;
&lt;br&gt;
Binary updated to latest revision, contains several bug fixes for IPv6 and full IPv6 support for control and data connections. Slight API change, EnableIPv6 property removed. If you connect to a IPv6 address everything is handled transparently behind the scenes.
 If you don&amp;#39;t want use IPv6 consider doing DNS resolution yourself and only connecting to IPv4 addresses.&lt;br&gt;
&lt;br&gt;
-- Updates 2012.10.02.02 --&lt;br&gt;
&lt;br&gt;
1. Fixed problem with GlobalScape&amp;#39;s secure FTP server and data connection SSL authentication.&lt;br&gt;
2. Fixed problem with improper sequencing of PBSZ and PROT commands in regards to requirements outlined by RFC 2228&lt;br&gt;
&lt;br&gt;
-- Updates 12.12.13.0 --&lt;br&gt;
&lt;br&gt;
1. Fixed bugs with thread safe data channels, see commit notes.&lt;br&gt;
2. Fixed bug in SSL validation behavior, you no longer are required to set the Accept property of the event args to True when the SSL certificate is valid.&lt;br&gt;
3. SSL Bug fix in active mode transfers&lt;br&gt;
4. Added support for client ssl certificates though this feature has not been tested or confirmed to be working. That doesn&amp;#39;t mean it doesn&amp;#39;t work, I just don&amp;#39;t have a way to confirm that it indeed does and the person who requested it hasn&amp;#39;t
 confirmed that it works for them.&lt;br&gt;
&lt;br&gt;
-- Updates 13.01.25.0 --&lt;br&gt;
&lt;br&gt;
1. Added support for NLST using the FtpListOptions.NameList flag. This approach to file listings is the slowest of the bunch however with the proper features on the server side it is the most accurate way to get a file listing with modification times and file
 size.&lt;br&gt;
2. Fixed bug in MLSD parser where items would fail because the line didn&amp;#39;t begin with ^type=&lt;br&gt;
3. Added check to GetListing() when using LIST where if the modification date is in the future and the MDTM command is supported the server is queried again for the correct modification time. This is feature exists because unix style long listings omit the
 year in certain situations which can potentially cause a modification time to be off by a year.&lt;br&gt;
4. Added support for parsing VAX/OpenVMS style directory listings. VAX/OpenVMS style paths are not supported however this limitation can be overcome by manually changing to the appropriate directories on the server instead of passing full paths to FtpClient
 method calls.&lt;br&gt;
5. Fixed bug in CreateDirectory() where 2 attempts to create a directory were made because the path ended with a slash.&lt;br&gt;
&lt;br&gt;
This code should be stable for most if not all people so I&amp;#39;ve changed the download status accordingly. As usual, if you find any bugs please report them or share your fixes. We may not be prompt in getting back to you 100% of the time but we indeed try
 to address problems in a timely manner.&lt;br&gt;
&lt;br&gt;
-- Updates 13.4.25.0 --&lt;br&gt;
&lt;br&gt;
Lots of changes... here&amp;#39;s a copy and paste from the commit comments:&lt;br&gt;
&lt;br&gt;
1. Added IFtpClient, IFtpListItem and IFtpReply interfaces to assist with MoQ unit testing. No testing has been done.&lt;br&gt;
&lt;br&gt;
2. Fixed bug with restart (REST) sequencing in OpenRead()&lt;br&gt;
&lt;br&gt;
3. More precise server feature matching to avoid false positives.&lt;br&gt;
&lt;br&gt;
4. Bug fix in IIS listing date/time parser.&lt;br&gt;
&lt;br&gt;
5. Reduced socket poll connection test to 500 miliseconds.&lt;br&gt;
&lt;br&gt;
6. MLSD, MDTM and LIST with DOS format (IIS) dates are assumed to be UTC. UNIX and VAX LIST listings are assumed to be local. The basis for this change is that LIST on filezilla gives local date/time values however MDTM and MLSD on filezilla give UTC date/time
 values. This might become an adjustable property of FtpClient in the future since all servers won&amp;#39;t behave the same in regards to timezones.&lt;br&gt;
&lt;br&gt;
7. Changed date/time parsing code to assume UTC date/time values are being returned from the server. Made modification to Connect() method in effort to detect when there is a disruption immediately upon the initial connection, i.e., before the server greeting
 can be read. An IOException is thrown when this happens instead of an empty FtpCommandException (what previously happened).&lt;br&gt;
&lt;br&gt;
8. Added code to FtpClient.Execute to detect stale data on the socket, generally due to a timeout &amp;#43; disconnection by the server. The server will sometimes send a disconnection notice that might be sitting in the buffer which breaks the Poll() connectivity test
 so the data is read and discarded. This still doesn&amp;#39;t guarantee a graceful reconnection, you need to catch IOException&amp;#39;s when you make calls to FtpClient&amp;#39;s method and look for the InnerException to be a SocketException, i.e.,&lt;br&gt;
&lt;br&gt;
try { conn.DoSomething() } catch(IOException e) { if(e.InnerException is SocketException) { // reconnect, DoSomething() again } }&lt;br&gt;
&lt;br&gt;
9. Fixed bug in socket polling code that was used to test for connectivity. Added new SocketPollInterval property (default 15 seconds) that is used to determine how much time should pass since the last read/write before the socket is Poll()&amp;#39;d for connectivity.
 Polling is used in conjunction with Socket.Connected because Socket.Connected still returns true even when the remote host has closed the connection.&lt;br&gt;
&lt;br&gt;
10. Slight refactoring of FtpSocketStream Connect() method to remove un-necessary exception handling. Added new SocketKeepAlive property that sets SocketOption.KeepAlive accordingly on the underlying stream sockets.&lt;br&gt;
&lt;br&gt;
11. Added support for distribution of System.Net.FtpClient through nuget: https://nuget.org/packages/System.Net.FtpClient/&lt;/div&gt;
&lt;div&gt;&lt;/div&gt;
</description><author></author><pubDate>Thu, 25 Apr 2013 15:34:55 GMT</pubDate><guid isPermaLink="false">Released: System.Net.FtpClient 13.4.25.0 (Apr 25, 2013) 20130425033455P</guid></item><item><title>Updated Release: System.Net.FtpClient 13.01.25.0 (Jan 25, 2013)</title><link>http://netftp.codeplex.com/releases/view/95632</link><description>&lt;div class="wikidoc"&gt;This is the first release of the new code base. It is not compatible with the old API, I repeat it is not a drop in update for projects currently using System.Net.FtpClient. New users should download this release. The old code base (Branch: System.Net.FtpClient_1) will continue to be supported while the new code matures. &lt;br /&gt;&lt;br /&gt;This release is a complete re-write of System.Net.FtpClient. The API and code are simpler than ever before. There are some new features included as well as an attempt at better thread safety. Multiple transfers from a single FtpClient object are now supported and async methods are available for nearly every method in FtpClient.&lt;br /&gt;&lt;br /&gt;Support for the FtpFile and FtpDirectory classes have been dropped in favor of the simpler FtpListItem objects. There are no plans to re-introduce these classes in the future.&lt;br /&gt;&lt;br /&gt;Support for the Upload(), Download() and Append() methods has been dropped and there are no plans to re-introduce them. There are however plenty of examples using the OpenRead(), OpenWrite() and OpenAppend() methods.&lt;br /&gt;&lt;br /&gt;The new CHM API reference includes examples for nearly every method in FtpClient including information about debugging and adding custom file listing parsers.&lt;br /&gt;&lt;br /&gt;-- Updates 2012.10.02.01 --&lt;br /&gt;&lt;br /&gt;Binary updated to latest revision, contains several bug fixes for IPv6 and full IPv6 support for control and data connections. Slight API change, EnableIPv6 property removed. If you connect to a IPv6 address everything is handled transparently behind the scenes. If you don&amp;#39;t want use IPv6 consider doing DNS resolution yourself and only connecting to IPv4 addresses.&lt;br /&gt;&lt;br /&gt;-- Updates 2012.10.02.02 --&lt;br /&gt;&lt;br /&gt;1. Fixed problem with GlobalScape&amp;#39;s secure FTP server and data connection SSL authentication.&lt;br /&gt;2. Fixed problem with improper sequencing of PBSZ and PROT commands in regards to requirements outlined by RFC 2228&lt;br /&gt;&lt;br /&gt;-- Updates 12.12.13.0 --&lt;br /&gt;&lt;br /&gt;1. Fixed bugs with thread safe data channels, see commit notes.&lt;br /&gt;2. Fixed bug in SSL validation behavior, you no longer are required to set the Accept property of the event args to True when the SSL certificate is valid.&lt;br /&gt;3. SSL Bug fix in active mode transfers&lt;br /&gt;4. Added support for client ssl certificates though this feature has not been tested or confirmed to be working. That doesn&amp;#39;t mean it doesn&amp;#39;t work, I just don&amp;#39;t have a way to confirm that it indeed does and the person who requested it hasn&amp;#39;t confirmed that it works for them.&lt;br /&gt;&lt;br /&gt;-- Updates 13.01.25.0 --&lt;br /&gt;&lt;br /&gt;1. Added support for NLST using the FtpListOptions.NameList flag. This approach to file listings is the slowest of the bunch however with the proper features on the server side it is the most accurate way to get a file listing with modification times and file size.&lt;br /&gt;2. Fixed bug in MLSD parser where items would fail because the line didn&amp;#39;t begin with ^type=&lt;br /&gt;3. Added check to GetListing() when using LIST where if the modification date is in the future and the MDTM command is supported the server is queried again for the correct modification time. This is feature exists because unix style long listings omit the year in certain situations which can potentially cause a modification time to be off by a year.&lt;br /&gt;4. Added support for parsing VAX/OpenVMS style directory listings. VAX/OpenVMS style paths are not supported however this limitation can be overcome by manually changing to the appropriate directories on the server instead of passing full paths to FtpClient method calls.&lt;br /&gt;5. Fixed bug in CreateDirectory() where 2 attempts to create a directory were made because the path ended with a slash.&lt;br /&gt;&lt;br /&gt;This code should be stable for most if not all people so I&amp;#39;ve changed the download status accordingly. As usual, if you find any bugs please report them or share your fixes. We may not be prompt in getting back to you 100% of the time but we indeed try to address problems in a timely manner.&lt;/div&gt;&lt;div class="ClearBoth"&gt;&lt;/div&gt;</description><author>jptrosclair</author><pubDate>Fri, 25 Jan 2013 15:15:14 GMT</pubDate><guid isPermaLink="false">Updated Release: System.Net.FtpClient 13.01.25.0 (Jan 25, 2013) 20130125031514P</guid></item><item><title>Released: System.Net.FtpClient 13.01.25.0 (Jan 25, 2013)</title><link>http://netftp.codeplex.com/releases/view/95632</link><description>
&lt;div class="wikidoc"&gt;This is the first release of the new code base. It is not compatible with the old API, I repeat it is not a drop in update for projects currently using System.Net.FtpClient. New users should download this release. The old code base (Branch:
 System.Net.FtpClient_1) will continue to be supported while the new code matures.
&lt;br&gt;
&lt;br&gt;
This release is a complete re-write of System.Net.FtpClient. The API and code are simpler than ever before. There are some new features included as well as an attempt at better thread safety. Multiple transfers from a single FtpClient object are now supported
 and async methods are available for nearly every method in FtpClient.&lt;br&gt;
&lt;br&gt;
Support for the FtpFile and FtpDirectory classes have been dropped in favor of the simpler FtpListItem objects. There are no plans to re-introduce these classes in the future.&lt;br&gt;
&lt;br&gt;
Support for the Upload(), Download() and Append() methods has been dropped and there are no plans to re-introduce them. There are however plenty of examples using the OpenRead(), OpenWrite() and OpenAppend() methods.&lt;br&gt;
&lt;br&gt;
The new CHM API reference includes examples for nearly every method in FtpClient including information about debugging and adding custom file listing parsers.&lt;br&gt;
&lt;br&gt;
-- Updates 2012.10.02.01 --&lt;br&gt;
&lt;br&gt;
Binary updated to latest revision, contains several bug fixes for IPv6 and full IPv6 support for control and data connections. Slight API change, EnableIPv6 property removed. If you connect to a IPv6 address everything is handled transparently behind the scenes.
 If you don&amp;#39;t want use IPv6 consider doing DNS resolution yourself and only connecting to IPv4 addresses.&lt;br&gt;
&lt;br&gt;
-- Updates 2012.10.02.02 --&lt;br&gt;
&lt;br&gt;
1. Fixed problem with GlobalScape&amp;#39;s secure FTP server and data connection SSL authentication.&lt;br&gt;
2. Fixed problem with improper sequencing of PBSZ and PROT commands in regards to requirements outlined by RFC 2228&lt;br&gt;
&lt;br&gt;
-- Updates 12.12.13.0 --&lt;br&gt;
&lt;br&gt;
1. Fixed bugs with thread safe data channels, see commit notes.&lt;br&gt;
2. Fixed bug in SSL validation behavior, you no longer are required to set the Accept property of the event args to True when the SSL certificate is valid.&lt;br&gt;
3. SSL Bug fix in active mode transfers&lt;br&gt;
4. Added support for client ssl certificates though this feature has not been tested or confirmed to be working. That doesn&amp;#39;t mean it doesn&amp;#39;t work, I just don&amp;#39;t have a way to confirm that it indeed does and the person who requested it hasn&amp;#39;t
 confirmed that it works for them.&lt;br&gt;
&lt;br&gt;
-- Updates 13.01.25.0 --&lt;br&gt;
&lt;br&gt;
1. Added support for NLST using the FtpListOptions.NameList flag. This approach to file listings is the slowest of the bunch however with the proper features on the server side it is the most accurate way to get a file listing with modification times and file
 size.&lt;br&gt;
2. Fixed bug in MLSD parser where items would fail because the line didn&amp;#39;t begin with ^type=&lt;br&gt;
3. Added check to GetListing() when using LIST where if the modification date is in the future and the MDTM command is supported the server is queried again for the correct modification time. This is feature exists because unix style long listings omit the
 year in certain situations which can potentially cause a modification time to be off by a year.&lt;br&gt;
4. Added support for parsing VAX/OpenVMS style directory listings. VAX/OpenVMS style paths are not supported however this limitation can be overcome by manually changing to the appropriate directories on the server instead of passing full paths to FtpClient
 method calls.&lt;br&gt;
5. Fixed bug in CreateDirectory() where 2 attempts to create a directory were made because the path ended with a slash.&lt;br&gt;
&lt;br&gt;
This code should be stable for most if not all people so I&amp;#39;ve changed the download status accordingly. As usual, if you find any bugs please report them or share your fixes. We may not be prompt in getting back to you 100% of the time but we indeed try
 to address problems in a timely manner.&lt;/div&gt;
&lt;div&gt;&lt;/div&gt;
</description><author></author><pubDate>Fri, 25 Jan 2013 15:15:14 GMT</pubDate><guid isPermaLink="false">Released: System.Net.FtpClient 13.01.25.0 (Jan 25, 2013) 20130125031514P</guid></item><item><title>Updated Release: System.Net.FtpClient 12.12.13.3 (Dec 13, 2012)</title><link>http://netftp.codeplex.com/releases/view/95632</link><description>&lt;div class="wikidoc"&gt;This is the first release of the new code base. It is not compatible with the old API, I repeat it is not a drop in update for projects currently using System.Net.FtpClient. New users should download this release. The old code base (Branch: System.Net.FtpClient_1) will continue to be supported while the new code matures. &lt;br /&gt;&lt;br /&gt;This release is a complete re-write of System.Net.FtpClient. The API and code are simpler than ever before. There are some new features included as well as an attempt at better thread safety. Multiple transfers from a single FtpClient object are now supported and async methods are available for nearly every method in FtpClient.&lt;br /&gt;&lt;br /&gt;Support for the FtpFile and FtpDirectory classes have been dropped in favor of the simpler FtpListItem objects. There are no plans to re-introduce these classes in the future.&lt;br /&gt;&lt;br /&gt;Support for the Upload(), Download() and Append() methods has been dropped and there are no plans to re-introduce them. There are however plenty of examples using the OpenRead(), OpenWrite() and OpenAppend() methods.&lt;br /&gt;&lt;br /&gt;The new CHM API reference includes examples for nearly every method in FtpClient including information about debugging and adding custom file listing parsers.&lt;br /&gt;&lt;br /&gt;-- Updates 2012.10.02.01 --&lt;br /&gt;&lt;br /&gt;Binary updated to latest revision, contains several bug fixes for IPv6 and full IPv6 support for control and data connections. Slight API change, EnableIPv6 property removed. If you connect to a IPv6 address everything is handled transparently behind the scenes. If you don&amp;#39;t want use IPv6 consider doing DNS resolution yourself and only connecting to IPv4 addresses.&lt;br /&gt;&lt;br /&gt;-- Updates 2012.10.02.02 --&lt;br /&gt;&lt;br /&gt;1. Fixed problem with GlobalScape&amp;#39;s secure FTP server and data connection SSL authentication.&lt;br /&gt;2. Fixed problem with improper sequencing of PBSZ and PROT commands in regards to requirements outlined by RFC 2228&lt;br /&gt;&lt;br /&gt;-- Updates 12.12.13.0 --&lt;br /&gt;&lt;br /&gt;1. Fixed bugs with thread safe data channels, see commit notes.&lt;br /&gt;2. Fixed bug in SSL validation behavior, you no longer are required to set the Accept property of the event args to True when the SSL certificate is valid.&lt;br /&gt;3. SSL Bug fix in active mode transfers&lt;br /&gt;4. Added support for client ssl certificates though this feature has not been tested or confirmed to be working. That doesn&amp;#39;t mean it doesn&amp;#39;t work, I just don&amp;#39;t have a way to confirm that it indeed does and the person who requested it hasn&amp;#39;t confirmed that it works for them.&lt;/div&gt;&lt;div class="ClearBoth"&gt;&lt;/div&gt;</description><author>jptrosclair</author><pubDate>Thu, 13 Dec 2012 14:51:40 GMT</pubDate><guid isPermaLink="false">Updated Release: System.Net.FtpClient 12.12.13.3 (Dec 13, 2012) 20121213025140P</guid></item><item><title>Released: System.Net.FtpClient 12.12.13.3 (Dec 13, 2012)</title><link>http://netftp.codeplex.com/releases/view/95632</link><description>
&lt;div class="wikidoc"&gt;This is the first release of the new code base. It is not compatible with the old API, I repeat it is not a drop in update for projects currently using System.Net.FtpClient. New users should download this release. The old code base (Branch:
 System.Net.FtpClient_1) will continue to be supported while the new code matures.
&lt;br&gt;
&lt;br&gt;
This release is a complete re-write of System.Net.FtpClient. The API and code are simpler than ever before. There are some new features included as well as an attempt at better thread safety. Multiple transfers from a single FtpClient object are now supported
 and async methods are available for nearly every method in FtpClient.&lt;br&gt;
&lt;br&gt;
Support for the FtpFile and FtpDirectory classes have been dropped in favor of the simpler FtpListItem objects. There are no plans to re-introduce these classes in the future.&lt;br&gt;
&lt;br&gt;
Support for the Upload(), Download() and Append() methods has been dropped and there are no plans to re-introduce them. There are however plenty of examples using the OpenRead(), OpenWrite() and OpenAppend() methods.&lt;br&gt;
&lt;br&gt;
The new CHM API reference includes examples for nearly every method in FtpClient including information about debugging and adding custom file listing parsers.&lt;br&gt;
&lt;br&gt;
-- Updates 2012.10.02.01 --&lt;br&gt;
&lt;br&gt;
Binary updated to latest revision, contains several bug fixes for IPv6 and full IPv6 support for control and data connections. Slight API change, EnableIPv6 property removed. If you connect to a IPv6 address everything is handled transparently behind the scenes.
 If you don&amp;#39;t want use IPv6 consider doing DNS resolution yourself and only connecting to IPv4 addresses.&lt;br&gt;
&lt;br&gt;
-- Updates 2012.10.02.02 --&lt;br&gt;
&lt;br&gt;
1. Fixed problem with GlobalScape&amp;#39;s secure FTP server and data connection SSL authentication.&lt;br&gt;
2. Fixed problem with improper sequencing of PBSZ and PROT commands in regards to requirements outlined by RFC 2228&lt;br&gt;
&lt;br&gt;
-- Updates 12.12.13.0 --&lt;br&gt;
&lt;br&gt;
1. Fixed bugs with thread safe data channels, see commit notes.&lt;br&gt;
2. Fixed bug in SSL validation behavior, you no longer are required to set the Accept property of the event args to True when the SSL certificate is valid.&lt;br&gt;
3. SSL Bug fix in active mode transfers&lt;br&gt;
4. Added support for client ssl certificates though this feature has not been tested or confirmed to be working. That doesn&amp;#39;t mean it doesn&amp;#39;t work, I just don&amp;#39;t have a way to confirm that it indeed does and the person who requested it hasn&amp;#39;t
 confirmed that it works for them.&lt;/div&gt;
&lt;div&gt;&lt;/div&gt;
</description><author></author><pubDate>Thu, 13 Dec 2012 14:51:40 GMT</pubDate><guid isPermaLink="false">Released: System.Net.FtpClient 12.12.13.3 (Dec 13, 2012) 20121213025140P</guid></item><item><title>Updated Release: System.Net.FtpClient 12.10.2.2 (Oct 02, 2012)</title><link>http://netftp.codeplex.com/releases/view/95632</link><description>&lt;div class="wikidoc"&gt;This is the first release of the new code base. It is not compatible with the old API, I repeat it is not a drop in update for projects currently using System.Net.FtpClient. New users should download this release. The old code base (Branch: System.Net.FtpClient_1) will continue to be supported while the new code matures. &lt;br /&gt;&lt;br /&gt;This release is a complete re-write of System.Net.FtpClient. The API and code are simpler than ever before. There are some new features included as well as an attempt at better thread safety. Multiple transfers from a single FtpClient object are now supported and async methods are available for nearly every method in FtpClient.&lt;br /&gt;&lt;br /&gt;Support for the FtpFile and FtpDirectory classes have been dropped in favor of the simpler FtpListItem objects. There are no plans to re-introduce these classes in the future.&lt;br /&gt;&lt;br /&gt;Support for the Upload(), Download() and Append() methods has been dropped and there are no plans to re-introduce them. There are however plenty of examples using the OpenRead(), OpenWrite() and OpenAppend() methods.&lt;br /&gt;&lt;br /&gt;The new CHM API reference includes examples for nearly every method in FtpClient including information about debugging and adding custom file listing parsers.&lt;br /&gt;&lt;br /&gt;-- Updates 2012.10.02.01 --&lt;br /&gt;&lt;br /&gt;Binary updated to latest revision, contains several bug fixes for IPv6 and full IPv6 support for control and data connections. Slight API change, EnableIPv6 property removed. If you connect to a IPv6 address everything is handled transparently behind the scenes. If you don&amp;#39;t want use IPv6 consider doing DNS resolution yourself and only connecting to IPv4 addresses.&lt;br /&gt;&lt;br /&gt;-- Updates 2012.10.02.02 --&lt;br /&gt;&lt;br /&gt;1. Fixed problem with GlobalScape&amp;#39;s secure FTP server and data connection SSL authentication.&lt;br /&gt;2. Fixed problem with improper sequencing of PBSZ and PROT commands in regards to requirements outlined by RFC 2228&lt;/div&gt;&lt;div class="ClearBoth"&gt;&lt;/div&gt;</description><author>jptrosclair</author><pubDate>Tue, 23 Oct 2012 13:28:09 GMT</pubDate><guid isPermaLink="false">Updated Release: System.Net.FtpClient 12.10.2.2 (Oct 02, 2012) 20121023012809P</guid></item><item><title>Released: System.Net.FtpClient 12.10.2.2 (paź 02, 2012)</title><link>http://netftp.codeplex.com/releases/view/95632</link><description>
&lt;div class="wikidoc"&gt;This is the first release of the new code base. It is not compatible with the old API, I repeat it is not a drop in update for projects currently using System.Net.FtpClient. New users should download this release. The old code base (Branch:
 System.Net.FtpClient_1) will continue to be supported while the new code matures.
&lt;br&gt;
&lt;br&gt;
This release is a complete re-write of System.Net.FtpClient. The API and code are simpler than ever before. There are some new features included as well as an attempt at better thread safety. Multiple transfers from a single FtpClient object are now supported
 and async methods are available for nearly every method in FtpClient.&lt;br&gt;
&lt;br&gt;
Support for the FtpFile and FtpDirectory classes have been dropped in favor of the simpler FtpListItem objects. There are no plans to re-introduce these classes in the future.&lt;br&gt;
&lt;br&gt;
Support for the Upload(), Download() and Append() methods has been dropped and there are no plans to re-introduce them. There are however plenty of examples using the OpenRead(), OpenWrite() and OpenAppend() methods.&lt;br&gt;
&lt;br&gt;
The new CHM API reference includes examples for nearly every method in FtpClient including information about debugging and adding custom file listing parsers.&lt;br&gt;
&lt;br&gt;
-- Updates 2012.10.02.01 --&lt;br&gt;
&lt;br&gt;
Binary updated to latest revision, contains several bug fixes for IPv6 and full IPv6 support for control and data connections. Slight API change, EnableIPv6 property removed. If you connect to a IPv6 address everything is handled transparently behind the scenes.
 If you don&amp;#39;t want use IPv6 consider doing DNS resolution yourself and only connecting to IPv4 addresses.&lt;br&gt;
&lt;br&gt;
-- Updates 2012.10.02.02 --&lt;br&gt;
&lt;br&gt;
1. Fixed problem with GlobalScape&amp;#39;s secure FTP server and data connection SSL authentication.&lt;br&gt;
2. Fixed problem with improper sequencing of PBSZ and PROT commands in regards to requirements outlined by RFC 2228&lt;/div&gt;
&lt;div&gt;&lt;/div&gt;
</description><author></author><pubDate>Tue, 23 Oct 2012 13:28:09 GMT</pubDate><guid isPermaLink="false">Released: System.Net.FtpClient 12.10.2.2 (paź 02, 2012) 20121023012809P</guid></item><item><title>Updated Release: System.Net.FtpClient 2012.10.02.02 (Oct 02, 2012)</title><link>http://netftp.codeplex.com/releases/view/95632</link><description>&lt;div class="wikidoc"&gt;This is the first release of the new code base. It is not compatible with the old API, I repeat it is not a drop in update for projects currently using System.Net.FtpClient. New users should download this release. The old code base (Branch: System.Net.FtpClient_1) will continue to be supported while the new code matures. &lt;br /&gt;&lt;br /&gt;This release is a complete re-write of System.Net.FtpClient. The API and code are simpler than ever before. There are some new features included as well as an attempt at better thread safety. Multiple transfers from a single FtpClient object are now supported and async methods are available for nearly every method in FtpClient.&lt;br /&gt;&lt;br /&gt;Support for the FtpFile and FtpDirectory classes have been dropped in favor of the simpler FtpListItem objects. There are no plans to re-introduce these classes in the future.&lt;br /&gt;&lt;br /&gt;Support for the Upload(), Download() and Append() methods has been dropped and there are no plans to re-introduce them. There are however plenty of examples using the OpenRead(), OpenWrite() and OpenAppend() methods.&lt;br /&gt;&lt;br /&gt;The new CHM API reference includes examples for nearly every method in FtpClient including information about debugging and adding custom file listing parsers.&lt;br /&gt;&lt;br /&gt;-- Updates 2012.10.02.01 --&lt;br /&gt;&lt;br /&gt;Binary updated to latest revision, contains several bug fixes for IPv6 and full IPv6 support for control and data connections. Slight API change, EnableIPv6 property removed. If you connect to a IPv6 address everything is handled transparently behind the scenes. If you don&amp;#39;t want use IPv6 consider doing DNS resolution yourself and only connecting to IPv4 addresses.&lt;br /&gt;&lt;br /&gt;-- Updates 2012.10.02.02 --&lt;br /&gt;&lt;br /&gt;1. Fixed problem with GlobalScape&amp;#39;s secure FTP server and data connection SSL authentication.&lt;br /&gt;2. Fixed problem with improper sequencing of PBSZ and PROT commands in regards to requirements outlined by RFC 2228&lt;/div&gt;&lt;div class="ClearBoth"&gt;&lt;/div&gt;</description><author>jptrosclair</author><pubDate>Fri, 19 Oct 2012 13:16:59 GMT</pubDate><guid isPermaLink="false">Updated Release: System.Net.FtpClient 2012.10.02.02 (Oct 02, 2012) 20121019011659P</guid></item><item><title>Released: System.Net.FtpClient 2012.10.02.02 (paź 02, 2012)</title><link>http://netftp.codeplex.com/releases/view/95632</link><description>
&lt;div class="wikidoc"&gt;This is the first release of the new code base. It is not compatible with the old API, I repeat it is not a drop in update for projects currently using System.Net.FtpClient. New users should download this release. The old code base (Branch:
 System.Net.FtpClient_1) will continue to be supported while the new code matures.
&lt;br&gt;
&lt;br&gt;
This release is a complete re-write of System.Net.FtpClient. The API and code are simpler than ever before. There are some new features included as well as an attempt at better thread safety. Multiple transfers from a single FtpClient object are now supported
 and async methods are available for nearly every method in FtpClient.&lt;br&gt;
&lt;br&gt;
Support for the FtpFile and FtpDirectory classes have been dropped in favor of the simpler FtpListItem objects. There are no plans to re-introduce these classes in the future.&lt;br&gt;
&lt;br&gt;
Support for the Upload(), Download() and Append() methods has been dropped and there are no plans to re-introduce them. There are however plenty of examples using the OpenRead(), OpenWrite() and OpenAppend() methods.&lt;br&gt;
&lt;br&gt;
The new CHM API reference includes examples for nearly every method in FtpClient including information about debugging and adding custom file listing parsers.&lt;br&gt;
&lt;br&gt;
-- Updates 2012.10.02.01 --&lt;br&gt;
&lt;br&gt;
Binary updated to latest revision, contains several bug fixes for IPv6 and full IPv6 support for control and data connections. Slight API change, EnableIPv6 property removed. If you connect to a IPv6 address everything is handled transparently behind the scenes.
 If you don&amp;#39;t want use IPv6 consider doing DNS resolution yourself and only connecting to IPv4 addresses.&lt;br&gt;
&lt;br&gt;
-- Updates 2012.10.02.02 --&lt;br&gt;
&lt;br&gt;
1. Fixed problem with GlobalScape&amp;#39;s secure FTP server and data connection SSL authentication.&lt;br&gt;
2. Fixed problem with improper sequencing of PBSZ and PROT commands in regards to requirements outlined by RFC 2228&lt;/div&gt;
&lt;div&gt;&lt;/div&gt;
</description><author></author><pubDate>Fri, 19 Oct 2012 13:16:59 GMT</pubDate><guid isPermaLink="false">Released: System.Net.FtpClient 2012.10.02.02 (paź 02, 2012) 20121019011659P</guid></item><item><title>Updated Release: System.Net.FtpClient 2012.08.08 (Aug 08, 2012)</title><link>http://netftp.codeplex.com/releases/view/92439</link><description>&lt;div class="wikidoc"&gt;This release is based on the old code base. No new features will be added. Bug fixes will come as needed to support people who have already invested time with this API. This code base has it&amp;#39;s own repository branch System.Net.FtpClient_1.&lt;br /&gt;&lt;br /&gt;---&lt;br /&gt;&lt;br /&gt;2012.08.08 Release. Several changes, see commit notes in source code section. CHM help as well as source for this release are included in the download. Remember that Windows 7 by default (and possibly older versions) will block you from opening the CHM by default due to trust settings. To get around the problem, right click on the CHM, choose properties and click the Un-block button.&lt;br /&gt;&lt;br /&gt;Please note that this will be the last release tested to compile with the .net 2.0 framework. I will be removing the project files for .net 2.0 and from here out only supporting .net 4.0.&lt;br /&gt;&lt;br /&gt;To pull the branch from this release, go to the source code section and select 2012.08.08 in the branch drop down or execute the following command:&lt;br /&gt;&lt;br /&gt;hg clone -u 2012.08.08 https://hg01.codeplex.com/netftp&lt;br /&gt;&lt;br /&gt;Thanks to all who have submitted code, feedback and made bug reports.&lt;/div&gt;&lt;div class="ClearBoth"&gt;&lt;/div&gt;</description><author>jptrosclair</author><pubDate>Thu, 04 Oct 2012 17:55:57 GMT</pubDate><guid isPermaLink="false">Updated Release: System.Net.FtpClient 2012.08.08 (Aug 08, 2012) 20121004055557P</guid></item><item><title>Released: System.Net.FtpClient 2012.08.08 (sie 08, 2012)</title><link>http://netftp.codeplex.com/releases/view/92439</link><description>
&lt;div class="wikidoc"&gt;This release is based on the old code base. No new features will be added. Bug fixes will come as needed to support people who have already invested time with this API. This code base has it&amp;#39;s own repository branch System.Net.FtpClient_1.&lt;br&gt;
&lt;br&gt;
---&lt;br&gt;
&lt;br&gt;
2012.08.08 Release. Several changes, see commit notes in source code section. CHM help as well as source for this release are included in the download. Remember that Windows 7 by default (and possibly older versions) will block you from opening the CHM by default
 due to trust settings. To get around the problem, right click on the CHM, choose properties and click the Un-block button.&lt;br&gt;
&lt;br&gt;
Please note that this will be the last release tested to compile with the .net 2.0 framework. I will be removing the project files for .net 2.0 and from here out only supporting .net 4.0.&lt;br&gt;
&lt;br&gt;
To pull the branch from this release, go to the source code section and select 2012.08.08 in the branch drop down or execute the following command:&lt;br&gt;
&lt;br&gt;
hg clone -u 2012.08.08 https://hg01.codeplex.com/netftp&lt;br&gt;
&lt;br&gt;
Thanks to all who have submitted code, feedback and made bug reports.&lt;/div&gt;
&lt;div&gt;&lt;/div&gt;
</description><author></author><pubDate>Thu, 04 Oct 2012 17:55:57 GMT</pubDate><guid isPermaLink="false">Released: System.Net.FtpClient 2012.08.08 (sie 08, 2012) 20121004055557P</guid></item><item><title>Updated Release: System.Net.FtpClient 2012.10.02.01 (Oct 02, 2012)</title><link>http://netftp.codeplex.com/releases/view/95632</link><description>&lt;div class="wikidoc"&gt;This is the first release of the new code base. It is not compatible with the old API, I repeat it is not a drop in update for projects currently using System.Net.FtpClient. New users should download this release. The old code base (Branch: System.Net.FtpClient_1) will continue to be supported while the new code matures. &lt;br /&gt;&lt;br /&gt;This release is a complete re-write of System.Net.FtpClient. The API and code are simpler than ever before. There are some new features included as well as an attempt at better thread safety. Multiple transfers from a single FtpClient object are now supported and async methods are available for nearly every method in FtpClient.&lt;br /&gt;&lt;br /&gt;Support for the FtpFile and FtpDirectory classes have been dropped in favor of the simpler FtpListItem objects. There are no plans to re-introduce these classes in the future.&lt;br /&gt;&lt;br /&gt;Support for the Upload(), Download() and Append() methods has been dropped and there are no plans to re-introduce them. There are however plenty of examples using the OpenRead(), OpenWrite() and OpenAppend() methods.&lt;br /&gt;&lt;br /&gt;The new CHM API reference includes examples for nearly every method in FtpClient including information about debugging and adding custom file listing parsers.&lt;br /&gt;&lt;br /&gt;-- Updates --&lt;br /&gt;&lt;br /&gt;Binary updated to latest revision, contains several bug fixes for IPv6 and full IPv6 support for control and data connections. Slight API change, EnableIPv6 property removed. If you connect to a IPv6 address everything is handled transparently behind the scenes. If you don&amp;#39;t want use IPv6 consider doing DNS resolution yourself and only connecting to IPv4 addresses.&lt;/div&gt;&lt;div class="ClearBoth"&gt;&lt;/div&gt;</description><author>jptrosclair</author><pubDate>Thu, 04 Oct 2012 17:51:27 GMT</pubDate><guid isPermaLink="false">Updated Release: System.Net.FtpClient 2012.10.02.01 (Oct 02, 2012) 20121004055127P</guid></item><item><title>Released: System.Net.FtpClient 2012.10.02.01 (paź 02, 2012)</title><link>http://netftp.codeplex.com/releases/view/95632</link><description>
&lt;div class="wikidoc"&gt;This is the first release of the new code base. It is not compatible with the old API, I repeat it is not a drop in update for projects currently using System.Net.FtpClient. New users should download this release. The old code base (Branch:
 System.Net.FtpClient_1) will continue to be supported while the new code matures.
&lt;br&gt;
&lt;br&gt;
This release is a complete re-write of System.Net.FtpClient. The API and code are simpler than ever before. There are some new features included as well as an attempt at better thread safety. Multiple transfers from a single FtpClient object are now supported
 and async methods are available for nearly every method in FtpClient.&lt;br&gt;
&lt;br&gt;
Support for the FtpFile and FtpDirectory classes have been dropped in favor of the simpler FtpListItem objects. There are no plans to re-introduce these classes in the future.&lt;br&gt;
&lt;br&gt;
Support for the Upload(), Download() and Append() methods has been dropped and there are no plans to re-introduce them. There are however plenty of examples using the OpenRead(), OpenWrite() and OpenAppend() methods.&lt;br&gt;
&lt;br&gt;
The new CHM API reference includes examples for nearly every method in FtpClient including information about debugging and adding custom file listing parsers.&lt;br&gt;
&lt;br&gt;
-- Updates --&lt;br&gt;
&lt;br&gt;
Binary updated to latest revision, contains several bug fixes for IPv6 and full IPv6 support for control and data connections. Slight API change, EnableIPv6 property removed. If you connect to a IPv6 address everything is handled transparently behind the scenes.
 If you don&amp;#39;t want use IPv6 consider doing DNS resolution yourself and only connecting to IPv4 addresses.&lt;/div&gt;
&lt;div&gt;&lt;/div&gt;
</description><author></author><pubDate>Thu, 04 Oct 2012 17:51:27 GMT</pubDate><guid isPermaLink="false">Released: System.Net.FtpClient 2012.10.02.01 (paź 02, 2012) 20121004055127P</guid></item><item><title>Updated Release: System.Net.FtpClient 2012.10.02 (Oct 02, 2012)</title><link>http://netftp.codeplex.com/releases/view/95632</link><description>&lt;div class="wikidoc"&gt;This is the first release of the new code base. It is not compatible with the old API, I repeat it is not a drop in update for projects currently using System.Net.FtpClient. New users should download this release. The old code base (Branch: System.Net.FtpClient_1) will continue to be supported while the new code matures. &lt;br /&gt;&lt;br /&gt;This release is a complete re-write of System.Net.FtpClient. The API and code are simpler than ever before. There are some new features included as well as an attempt at better thread safety. Multiple transfers from a single FtpClient object are now supported and async methods are available for nearly every method in FtpClient.&lt;br /&gt;&lt;br /&gt;Support for the FtpFile and FtpDirectory classes have been dropped in favor of the simpler FtpListItem objects. There are no plans to re-introduce these classes in the future.&lt;br /&gt;&lt;br /&gt;Support for the Upload(), Download() and Append() methods has been dropped and there are no plans to re-introduce them. There are however plenty of examples using the OpenRead(), OpenWrite() and OpenAppend() methods.&lt;br /&gt;&lt;br /&gt;The new CHM API reference includes examples for nearly every method in FtpClient including information about debugging and adding custom file listing parsers.&lt;/div&gt;&lt;div class="ClearBoth"&gt;&lt;/div&gt;</description><author>jptrosclair</author><pubDate>Tue, 02 Oct 2012 20:46:07 GMT</pubDate><guid isPermaLink="false">Updated Release: System.Net.FtpClient 2012.10.02 (Oct 02, 2012) 20121002084607P</guid></item><item><title>Released: System.Net.FtpClient 2012.10.02 (paź 02, 2012)</title><link>http://netftp.codeplex.com/releases/view/95632</link><description>
&lt;div class="wikidoc"&gt;This is the first release of the new code base. It is not compatible with the old API, I repeat it is not a drop in update for projects currently using System.Net.FtpClient. New users should download this release. The old code base (Branch:
 System.Net.FtpClient_1) will continue to be supported while the new code matures.
&lt;br&gt;
&lt;br&gt;
This release is a complete re-write of System.Net.FtpClient. The API and code are simpler than ever before. There are some new features included as well as an attempt at better thread safety. Multiple transfers from a single FtpClient object are now supported
 and async methods are available for nearly every method in FtpClient.&lt;br&gt;
&lt;br&gt;
Support for the FtpFile and FtpDirectory classes have been dropped in favor of the simpler FtpListItem objects. There are no plans to re-introduce these classes in the future.&lt;br&gt;
&lt;br&gt;
Support for the Upload(), Download() and Append() methods has been dropped and there are no plans to re-introduce them. There are however plenty of examples using the OpenRead(), OpenWrite() and OpenAppend() methods.&lt;br&gt;
&lt;br&gt;
The new CHM API reference includes examples for nearly every method in FtpClient including information about debugging and adding custom file listing parsers.&lt;/div&gt;
&lt;div&gt;&lt;/div&gt;
</description><author></author><pubDate>Tue, 02 Oct 2012 20:46:07 GMT</pubDate><guid isPermaLink="false">Released: System.Net.FtpClient 2012.10.02 (paź 02, 2012) 20121002084607P</guid></item></channel></rss>