
The structure of a MarkupImageDataProvider is heirarchical such that a MarkupImageDataProvider derives from Microsoft's ProviderBase and is instantiated from settings specified in Web.confg. Through the OpenImageData() and OpenArtData() methods, the MarkupImageDataProvider opens a MarkupImageDataConnection or MarkupArtDataConnection. This is done so that the connection classes may store contextual information pertinent to that particular provider, ex. (and SQL Data Provider which requires a connection to an SQL database, or an FTP data provider, also requiring a connection). From the connection, a Document Data Connection is opened for a document with a particular identifier. The Document Data Connection classes contain methods that facilitate file operations. Both the Data Connection and Document Data Connection classes implement the IDisposable interface.
'Declaration Public MustInherit Class MarkupImageDataProvider Inherits System.Configuration.Provider.ProviderBase
'Usage Dim instance As MarkupImageDataProvider
public abstract class MarkupImageDataProvider : System.Configuration.Provider.ProviderBase
public __gc abstract class MarkupImageDataProvider : public System.Configuration.Provider.ProviderBase
public ref class MarkupImageDataProvider abstract : public System.Configuration.Provider.ProviderBase
Also, if creating a custom provider in a separate assembly, make sure that you add a reference to the .NET assembly "System.Configuration" in the references of the Visual Studio Solution Explorer as Data Providers derive from ProviderBase.
System.Object
System.Configuration.Provider.ProviderBase
ImageGear.Web.DataProviders.MarkupImageDataProvider
ImageGear.Web.DataProviders.MarkupFileImageDataProvider
ImageGear.Web.DataProviders.MarkupSqlImageDataProvider