CrescendoDLL Namespace Reference

The CrescendoDLL namespace contains classes and methods that allow the user to perform various operations with SmartCards by direct APDU communication. More...

Namespaces
namespace	PCSC
	The CrescendoDLL.PCSC namespace contains Enums relevant to public methods from the main CrescendoDLL namespace. It also contains internal methods and classes that represent the individual applets and applet commands.
namespace	USB_HID

Classes
class	Logger
	Logging class for logging messages with chosen severity. More...
class	SDKCore
	The SDKCore class contains all fundamental methods that can be used by the user to communicate with the SmartCard. More...

Enumerations
enum	DataType {   BIN , HEX , BASE64 , BASE64URL ,   UTF8 }
	Enum representing the different data types that can be converted to a byte array. More...
enum	LogLevel {   DEBUG , INFO , WARN , ERROR ,   SILENT }
	Enumeration representing different levels of logging. More...

Detailed Description

The CrescendoDLL namespace contains classes and methods that allow the user to perform various operations with SmartCards by direct APDU communication.

Enumeration Type Documentation

DataType

enum CrescendoDLL.DataType

Enum representing the different data types that can be converted to a byte array.

Enumerator
BIN	Binary data format. Used only when bytes should be read directly from a given file.
HEX	Hexadecimal string, where every two characters represent a byte.
BASE64	Base64 string, which can be directly converted to a byte array.
BASE64URL	Base64 URL string, which can be directly converted to a byte array.
UTF8	UTF8 string, where each character is converted to its UTF8 value to form a byte array.

LogLevel

enum CrescendoDLL.LogLevel

Enumeration representing different levels of logging.

Enumerator
DEBUG	Log detailed diagnostic information. This level includes raw APDU commands and responses, complete USB HID (CTAP) packet dumps, and granular step-by-step protocol traces. Ideal for in-depth troubleshooting. (Note: sensitive data within payloads is redacted by default).
INFO	Log high-level informational messages and confirmations that operations are proceeding as expected. Includes user prompts (e.g., "Please press the button on the device") and general token/reader enumeration results.
WARN	Log an indication that something unexpected happened, but the SDK is able to recover or safely continue. Examples include unexpected device responses, missing optional data objects, or non-fatal protocol mismatches.
ERROR	Log severe issues where the SDK has failed to perform a requested operation. Examples include critical PC/SC or HID communication failures, trapped exceptions, or unsupported hardware capabilities.
SILENT	Fully suppresses all log output. This is the recommended setting when consuming the SDK programmatically or when relying on pure data output (e.g., raw JSON) to standard output.