Partager via

  • Article

Classe ReportOperationsCollection

Represents a collection of report operations.

Espace de noms :  Microsoft.ReportingServices.Interfaces
Assemblys :   Microsoft.ReportingServices.SharePoint.UI.WebParts (dans Microsoft.ReportingServices.SharePoint.UI.WebParts.dll)
  Microsoft.ReportingServices.Interfaces (dans Microsoft.ReportingServices.Interfaces.dll)

Syntaxe

'Déclaration
<SerializableAttribute> _
Public NotInheritable Class ReportOperationsCollection _
    Inherits CollectionBase
'Utilisation
Dim instance As ReportOperationsCollection

[SerializableAttribute]
public sealed class ReportOperationsCollection : CollectionBase

[SerializableAttribute]
public ref class ReportOperationsCollection sealed : public CollectionBase

[<SealedAttribute>]
[<SerializableAttribute>]
type ReportOperationsCollection =  
    class
        inherit CollectionBase
    end

public final class ReportOperationsCollection extends CollectionBase

Notes

A ReportOperationsCollection object consists of a collection of ReportOperation enumeration values that correspond to the various folder 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..::..ReportOperationsCollection

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.