Table of Contents

Namespace NAPS2.Scan.Exceptions

Classes

AlreadyHandledDriverException

Indicates an exception that the driver already handled (i.e. gave the user an error message) and doesn't require further notification.

DeviceBusyException

Indicates the scanning device is busy with another operation. Maybe retry later.

DeviceCommunicationException

Indicates the connection with the scanning device was interrupted.

DeviceCoverOpenException

Indicates the scanning device's flatbed cover is open and needs to be closed before scanning.

DeviceException

Indicates an exception related to the physical device (e.g. offline, busy, paper jam).

DeviceFeederEmptyException

Indicates the scanning device's automatic document feeder (ADF) is empty and doesn't have any pages to scan.

DeviceNotFoundException

Indicates the scanning device could not be found. It may have been uninstalled or disconnected.

DeviceOfflineException

Indicates the scanning device is offline and a connection couldn't be established.

DevicePaperJamException

Indicates the scanning device's automatic document feeder (ADF) has a paper jam that needs to be cleared.

DeviceWarmingUpException

Indicates the scanning device is currently warming up and can't be interacted with.

DriverNotSupportedException

Indicates that a driver was selected that isn't supported with the current platform or framework.

NoDuplexSupportException

Indicates that PaperSource.Duplex was selected but the scanning device/driver doesn't support duplex scanning.

NoFeederSupportException

Indicates that PaperSource.Feeder was selected but the scanning device/driver doesn't support feeder scanning.

ScanDriverException

Indicates an exception with the scanning driver. The concrete class may be a well-known exception type (e.g. DeviceOfflineException) or an unknown exception (ScanDriverUnknownException).

ScanDriverUnknownException

Indicates an unknown exception with the scanning driver that should be logged with full diagnostics.