Classe DatasourceOperationsCollection
Represents a collection of data source operations.
Espace de noms : Microsoft.ReportingServices.Interfaces
Assemblys : Microsoft.ReportingServices.Interfaces (dans Microsoft.ReportingServices.Interfaces.dll)
Microsoft.ReportingServices.SharePoint.UI.WebParts (dans Microsoft.ReportingServices.SharePoint.UI.WebParts.dll)
Syntaxe
'Déclaration
<SerializableAttribute> _
Public NotInheritable Class DatasourceOperationsCollection _
Inherits CollectionBase
'Utilisation
Dim instance As DatasourceOperationsCollection
[SerializableAttribute]
public sealed class DatasourceOperationsCollection : CollectionBase
[SerializableAttribute]
public ref class DatasourceOperationsCollection sealed : public CollectionBase
[<SealedAttribute>]
[<SerializableAttribute>]
type DatasourceOperationsCollection =
class
inherit CollectionBase
end
public final class DatasourceOperationsCollection extends CollectionBase
Notes
A DatasourceOperationsCollection object consists of a collection of DatasourceOperation enumeration values that correspond to the various data source operations or actions that a user can perform in SQL Server Reporting Services.
Operation collections and operation enumerations support authorization in Reporting Services. The operations collection is one of the prime components of any access control entry (AceStruct object). The operations collection contains the list of operations permitted on an item in the report server database for a given principal name. As demonstrated in previous examples, evaluating the operation collections for an item is a key part of any Reporting Services authorization extension. There exists an operation collection for each of the securable item types in Reporting Services, including the catalog (general system operations), folders, reports, and resources.
Hiérarchie d'héritage
System. . :: . .Object
System.Collections. . :: . .CollectionBase
Microsoft.ReportingServices.Interfaces..::..DatasourceOperationsCollection
Sécurité des threads
Tous les membres publics static (Shared dans Visual Basic) de ce type sont thread-safe. Il n'est pas garanti que les membres d'instance soient thread-safe.