InvalidDataSourceReference-Klasse

Represents a state in which a data source reference is no longer valid.

Vererbungshierarchie

System.Object
  ReportService2005.DataSourceDefinitionOrReference
    ReportService2005.InvalidDataSourceReference

Namespace:  ReportService2005
Assembly:  ReportService2005 (in ReportService2005.dll)

Syntax

'Declaration
Public Class InvalidDataSourceReference _
    Inherits DataSourceDefinitionOrReference
'Usage
Dim instance As InvalidDataSourceReference

public class InvalidDataSourceReference : DataSourceDefinitionOrReference

public ref class InvalidDataSourceReference : public DataSourceDefinitionOrReference

type InvalidDataSourceReference =  
    class 
        inherit DataSourceDefinitionOrReference 
    end

public class InvalidDataSourceReference extends DataSourceDefinitionOrReference

Der InvalidDataSourceReference-Typ macht folgende Elemente verfügbar.

Konstruktoren

	Name	Beschreibung
	InvalidDataSourceReference	Initializes a new instance of the InvalidDataSourceReference class.

Zum Anfang

Methoden

	Name	Beschreibung
	Equals	(Geerbt von Object.)
	Finalize	(Geerbt von Object.)
	GetHashCode	(Geerbt von Object.)
	GetType	(Geerbt von Object.)
	MemberwiseClone	(Geerbt von Object.)
	ToString	(Geerbt von Object.)

Zum Anfang

Hinweise

An InvalidDataSourceReference object is used with the Item property as output by GetItemDataSources method.

In most cases, an InvalidDataSourceReference object is returned when a shared data source has been deleted.

To evaluate whether a data source reference is valid, use the is keyword in C# (TypeOf/Is in Visual Basic) to determine the type of object returned by the Item property of the DataSource class, as shown in the following C# code:

DataSource[] dataSource;
dataSource = service.GetReportDataSources( "/MyReport" );

foreach ( DataSource ds in dataSource )
{
    if ( ds.Item is InvalidDataSourceReference )
    {
        // Code to handle a corrupt or missing data source reference goes here...
    }
}

Threadsicherheit

Alle öffentlichen static (Shared in Visual Basic)-Elemente dieses Typs sind Threadsicher. Für Instanzelemente wird die Threadsicherheit nicht gewährleistet.

Siehe auch

Verweis

ReportService2005-Namespace