InnerDrive.Azure 5.3.1592

Inner Drive Extensible Architeture

The Inner Drive Extensible Architecture implements common .NET development situations including time zones, money, measurements and conversions, and Microsoft Azure features.

InnerDrive.Azure

Features

• Helper classes for Azure Blob Storage
• Helper classes to use Azure Key Vault features
• Helper classes to use Azure Table Storage features
• Azure support for InnerDrive.TimeZones features

Prerequisites

This package runs on .NET 10, with dependencies on InnerDrive.Core and InnerDrive.TimeZones.

To use this package, you'll also need a Microsoft Azure subscription.

Usage

The Inner Drive Technology website has a full SDK and example code. We also have a demo weather site that uses all the IDEA components.

Azure Blob storage for IANA Time Zone files

To use the AzureTzInfoFileReader with the IANA Time Zone database, add the following to your appSettings.config:

{
	"storageAccountKey": "your storage account key",
	"storageAccountName": "your storage account name",
	"storageConnectionString": "your storage account connection string",
	"timeZoneSettings": {
		"defaultTimeZoneHomeZone": "America/Chicago",
		"timeZoneBlobName": "timezones"
	}
}

Note that you can use either the storage account connection string or the key/name pair.

Azure Key Vault helper classes

To use the AzureKeyVaultXProvider classes (Crypto, Key, and Secret), add the following to your appSettings.config:

{
	"keyVaultSecretProviderThrowExceptions": true,
	"keyVaultSecretProviderTrace": true,
	"keyVaultTenantId": "your tenant ID",
	"keyVaultUrl": "your key vault FQDN"
}

Azure Table Storage helper classes

To use the AzureTableStore and AzureTableSettingStore classes, add the following to your appSettings.config:

{
	"settingsTableName": "the table name for your settings table",
	"storageAccountKey": "your storage account key",
	"storageAccountName": "your storage account name",
	"storageTablesUri": "your tables URI",
	"storageConnectionString": "your storage account connection string"
}

CLDR support for InnerDrive.TimeZones

We added support for Unicode's Common Locale Data Repository (CLDR) time zone data with release 5.3.9728 on 19 August 2026.

AzureCldrFileReader loads CLDR data from Azure Blob Storage instead of local disk, for applications that already keep their IANA time zone data in a Blob container. It expects the same layout as InnerDrive.TimeZones's LocalCldrFileReader: a metaZones.json blob at the container root, and one {locale}/timeZoneNames.json blob per staged locale (Azure Blob names can contain /, so this reads as an ordinary folder structure in Storage Explorer).

Uploading CLDR data to the blob container

1. Download the metaZones.json and timeZoneNames.json files you need from the cldr-json project, laid out locally the same way LocalCldrFileReader expects:

CldrData/
	metaZones.json
	en/
		timeZoneNames.json
	fr/
		timeZoneNames.json

2. Upload the whole tree with the Azure CLI, preserving the relative paths as blob names:

az storage blob upload-batch --account-name <your storage account> --destination cldrdata --source ./CldrData

Storage Explorer's drag-and-drop upload, keeping the subfolders intact, works just as well.

Retrieving CLDR data with AzureCldrFileReader

Add the following to your appSettings.json:

{
	"storageConnectionString": "your storage account connection string",
	"timeZoneSettings": {
		"cldrBlobName": "cldrdata",
		"cldrDefaultLocale": "en"
	}
}

Then supply the reader to TimeZoneFactory the same way you would LocalCldrFileReader:

var tzReader = new AzureTzInfoFileReader(Configuration);
var cldrReader = new AzureCldrFileReader(Configuration);
var factory = new TimeZoneFactory(Configuration, tzReader, cldrReader);
await factory.InitializeAsync();

As with the local reader, CLDR data is optional and non-fatal by default. See the InnerDrive.TimeZones README for the localized-name and picker-list APIs this unlocks.

Feedback

Comments or questions? Send feedback