Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://github.com/robinrodricks/FluentFTP/wiki/v40-Migration-Guide below:

v40 Migration Guide · robinrodricks/FluentFTP Wiki · GitHub

This guide helps you migrate from v39 and older releases to v40+ and newer releases.

FluentFTP has had a long and colorful history of development. While we have always strived to rapidly add features and release them often, we have not really had the time to design our API surface according to well-defined principles.

In this release our goals were to:

1. Cleanup the API surface
2. Improve the configuration methodology
3. Improve the logging methodology
4. Fix technical debt by dropping old frameworks
5. Modernize the codebase
6. Improve code organization

Instead of making multiple releases with constant breaking API changes, I decided to roll this into a single large release. v40 is the culmination of all of the above goals.

The full discussion can be found here.

The following is a brief overview on the major changes in v40+.

• FTP client classes split (FtpClient and AsyncFtpClient)
• Async API renamed
• Constructors refactored
• Interfaces refactored
• Configuration system modernized
• Logging modernized
• Dropped support for .NET Standard 1.2, 1.4 and .NET 2.0, 3.5, 4.0 and 4.5
• Added support for .NET 4.6.2 and 4.7.2
• Added a Nuget dependency on Microsoft.Extensions.Logging.Abstractions v2.1.0

The full release notes can be found here.

The FTP client has now been split into 2 main classes, FtpClient and AsyncFtpClient. You will have to select one client based on the type of API you need, and stick with that type of API for the lifetime of that class. It is no longer possible to mix sync and async API calls.

This table lists out all the clients available, including proxy clients:

The following constructors have been introduced:

• Synchronous version:

  • FtpClient()
  • FtpClient(string host, int port = 0, FtpConfig config = null, ILogger logger = null)
  • FtpClient(string host, string user, string pass, int port = 0, FtpConfig config = null, ILogger logger = null)
  • FtpClient(string host, NetworkCredential credentials, int port = 0, FtpConfig config = null, ILogger logger = null)

• Async version:

  • AsyncFtpClient()
  • AsyncFtpClient(string host, int port = 0, FtpConfig config = null, ILogger logger = null)
  • AsyncFtpClient(string host, string user, string pass, int port = 0, FtpConfig config = null, ILogger logger = null)
  • AsyncFtpClient(string host, NetworkCredential credentials, int port = 0, FtpConfig config = null, ILogger logger = null)

• You can always construct the client and then later set these properties:

  • client.Host
  • client.Port
  • client.Credentials
  • client.Config
  • client.Logger

The following constructors have been deleted:

• FtpClient()
• FtpClient(string host)
• FtpClient(string host, NetworkCredential credentials)
• FtpClient(string host, int port, NetworkCredential credentials)
• FtpClient(string host, string user, string pass)
• FtpClient(string host, string user, string pass, string account)
• FtpClient(string host, int port, string user, string pass)
• FtpClient(string host, int port, string user, string pass, string account)
• FtpClient(Uri host)
• FtpClient(Uri host, NetworkCredential credentials)
• FtpClient(Uri host, string user, string pass)
• FtpClient(Uri host, string user, string pass, string account)
• FtpClient(Uri host, int port, string user, string pass)
• FtpClient(Uri host, int port, string user, string pass, string account)

The interface IFtpClient has now been split into 2 interfaces: IFtpClient and IAsyncFtpClient.

If you have programmed against interfaces, you will have to select one interface based on the type of API you are using.

All async methods are now available inside AsyncFtpClient and they have the Async suffix removed.

The full list of changes are given below:

All of the configuration settings have now been moved into the Config property within the FtpClient objects. You can specify the config in the constructor (optional) and/or you can change individual properties at any time. You can also reassign the Config property on the fly at any time.

The full list of changes are given below:

A new logging system has been introduced, wherein each FtpClient can now have its own logger assigned which can directly utilize any logger that implements a custom IFtpLogger interface. A sister package called FluentFTP.Logging helps you integrate this with the industry-standard MELA ILogger interface.

• client.Logger allows you to specify any IFtpLogger, which can be linked to the industry-standard MELA logging system.
• You can also pass an ILogger instance in any client constructor
• You can reassign the client.Logger at any time
• You can set client.Logger to null to disable logging

using FluentFTP;          // from NuGet package FluentFTP
using FluentFTP.Logging;  // from NuGet package FluentFTP.Logging

var client = new FtpClient();
client.Logger = new FtpLogAdapter(new Log4NetLogger())

The older console logger has been preserved but renamed. It provides the in-built ability to log to console. If you run FluentFTP in debug mode by building from source, it will also log to the debug console.

• FtpTrace.LogToConsole renamed to client.Config.LogToConsole

An older logging callback system has been preserved but renamed. It provides an easy way to consume FTP logging events if you don't want to use the new ILogger system.

• client.OnLogEvent renamed to client.LegacyLogger

The older logging settings have been preserved:

• FtpTrace.LogIP renamed to client.Config.LogHost
• FtpTrace.LogUserName renamed to client.Config.LogUserName
• FtpTrace.LogPassword renamed to client.Config.LogPassword

The older logging system has been removed, wherein you had a static class FtpTrace responsible for logging.

• FtpTrace class
• FtpTrace.LogFunctions because logging function names is always enabled

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4