MultiFileConnectionManagerUIArgs Constructors
Definition
Important
Some information relates to prerelease product that may be substantially modified before it’s released. Microsoft makes no warranties, express or implied, with respect to the information provided here.
Initializes a new instance of the MultiFileConnectionManagerUIArgs class.
Overloads
| MultiFileConnectionManagerUIArgs() |
Initializes a new instance of the MultiFileConnectionManagerUIArgs class. |
| MultiFileConnectionManagerUIArgs(ICollection) |
Initializes a new instance of the MultiFileConnectionManagerUIArgs class, using a collection of DTSFileConnectionUsageType usage types specific to this connection. |
| MultiFileConnectionManagerUIArgs(String) |
Initializes a new instance of the MultiFileConnectionManagerUIArgs class using a String to specify what file types are valid for this connection. |
| MultiFileConnectionManagerUIArgs(String, ICollection) |
Initializes a new instance of the MultiFileConnectionManagerUIArgs class, initializing both the file type filter and the usage types. |
MultiFileConnectionManagerUIArgs()
Initializes a new instance of the MultiFileConnectionManagerUIArgs class.
public:
MultiFileConnectionManagerUIArgs();public MultiFileConnectionManagerUIArgs ();Public Sub New ()Applies to
MultiFileConnectionManagerUIArgs(ICollection)
Initializes a new instance of the MultiFileConnectionManagerUIArgs class, using a collection of DTSFileConnectionUsageType usage types specific to this connection.
public:
MultiFileConnectionManagerUIArgs(System::Collections::ICollection ^ supportedUsageTypes);public MultiFileConnectionManagerUIArgs (System.Collections.ICollection supportedUsageTypes);new Microsoft.SqlServer.Dts.Runtime.Design.MultiFileConnectionManagerUIArgs : System.Collections.ICollection -> Microsoft.SqlServer.Dts.Runtime.Design.MultiFileConnectionManagerUIArgsPublic Sub New (supportedUsageTypes As ICollection)Parameters
- supportedUsageTypes
- ICollection
A collection of DTSFileConnectionUsageType enumerations available to choose from.
Remarks
An empty collection implies that all usage types are supported.
The usage types are currently Create file, Existing file, Create folder, and Existing folder. The collection contains only those types that are valid for the connection. For example, in the FTP task, if the operation is to send files using FTP, then the local path can only be Existing file, as you can only transfer existing files.
Applies to
MultiFileConnectionManagerUIArgs(String)
Initializes a new instance of the MultiFileConnectionManagerUIArgs class using a String to specify what file types are valid for this connection.
public:
MultiFileConnectionManagerUIArgs(System::String ^ fileFilter);public MultiFileConnectionManagerUIArgs (string fileFilter);new Microsoft.SqlServer.Dts.Runtime.Design.MultiFileConnectionManagerUIArgs : string -> Microsoft.SqlServer.Dts.Runtime.Design.MultiFileConnectionManagerUIArgsPublic Sub New (fileFilter As String)Parameters
- fileFilter
- String
A file filter restricts the types of files offered in a user interface, such as *.txt.
Remarks
The default filter, if not specified, is to show all files. To limit the files shown, the fileFilter string can specify only those types that are valid for the connection. For example, in an XML task, you may only want the user to select XML files, so the fileFilter would be *.XML.
For each filtering option, the filter string contains a description of the filter, followed by the vertical bar (|) and the filter pattern. The strings for different filtering options are separated by a vertical bar.
The following is an example of a filter string:
"Text files (*.txt)|*.txt|All files (*.*)|*.*"
You can add several filter patterns to a filter by separating the file types with semicolons. For example:
"Image Files(*.BMP;*.JPG;*.GIF)|*.BMP;*.JPG;*.GIF|All files (*.*)|*.*"
The format and syntax of this fileFilter string is identical to the Filter property found on the OpenFileDialog class. For more information on "OpenFileDialog Class", see the .NET Framework Class Library.
Applies to
MultiFileConnectionManagerUIArgs(String, ICollection)
Initializes a new instance of the MultiFileConnectionManagerUIArgs class, initializing both the file type filter and the usage types.
public:
MultiFileConnectionManagerUIArgs(System::String ^ fileFilter, System::Collections::ICollection ^ supportedUsageTypes);public MultiFileConnectionManagerUIArgs (string fileFilter, System.Collections.ICollection supportedUsageTypes);new Microsoft.SqlServer.Dts.Runtime.Design.MultiFileConnectionManagerUIArgs : string * System.Collections.ICollection -> Microsoft.SqlServer.Dts.Runtime.Design.MultiFileConnectionManagerUIArgsPublic Sub New (fileFilter As String, supportedUsageTypes As ICollection)Parameters
- fileFilter
- String
A file filter restricts the types of files offered in a user interface, such as *.txt.
- supportedUsageTypes
- ICollection
A collection of DTSFileConnectionUsageType enumerations for usage types.
Remarks
For the fileFilter, the default filter, if no other filter is specified, is to show all files. To limit the files shown, the fileFilter string can specify only those types that are valid for the connection. For example, in an XML task, you may only want the user to select XML files, so the fileFilter would be *.XML.
For each filtering option, the filter string contains a description of the filter, followed by the vertical bar (|) and the filter pattern. The strings for different filtering options are separated by the vertical bar.
The following is an example of a filter string:
"Text files (*.txt)|*.txt|All files (*.*)|*.*"
You can add several filter patterns to a filter by separating the file types with semicolons. For example:
"Image Files(*.BMP;*.JPG;*.GIF)|*.BMP;*.JPG;*.GIF|All files (*.*)|*.*"
The format and syntax of this fileFilter string is identical to the Filter property found on the OpenFileDialog class. For more information , see the "OpenFileDialog Class" in the .NET Framework Class Library.
For the supportedUsageTypes, an empty collection implies that all usage types are supported.
The usage types are currently Create file, Existing file, Create folder, and Existing folder. The collection contains only those types that are valid for the connection. For example, in the FTP task, if the operation is to send files using FTP, then the local path can only be Existing file, as you can only transfer existing files.