👁 Image
AlexaVoxCraft.Lambda.Host 5.0.1.100

🔣 AlexaVoxCraft

AlexaVoxCraft is a modular C# .NET library for building Amazon Alexa skills using modern .NET practices. It provides comprehensive support for Alexa skill development with CQRS patterns, visual interfaces, and AWS Lambda hosting.

Key Features

• 🎯 MediatR Integration: CQRS-style request handling with compile-time source-generated DI registration
• 🎨 APL Support: Complete Alexa Presentation Language implementation for rich visual interfaces
• ⚡ Lambda Hosting: Optimized AWS Lambda runtime with custom serialization and ReadyToRun publishing
• 📊 Session Management: Robust session attribute handling and game state persistence
• 🔧 Pipeline Behaviors: Request/response interceptors for cross-cutting concerns like logging and validation
• 🧪 Testing Support: Comprehensive testing utilities with AutoFixture integration and property-based testing

📦 Packages

👁 Build Status

🚀 Quick Start

Install Core Packages

# Core MediatR integration and Lambda hosting
dotnet add package AlexaVoxCraft.MediatR.Lambda

# APL visual interface support (optional)
dotnet add package AlexaVoxCraft.Model.Apl

# OpenTelemetry observability (optional)
dotnet add package AlexaVoxCraft.Observability

# CloudWatch-compatible JSON logging (optional)
dotnet add package LayeredCraft.Logging.CompactJsonFormatter

Requirements

⚠️ SDK Version Required: To use source-generated dependency injection with interceptors, you must use at least version 8.0.400 of the .NET SDK. This ships with Visual Studio 2022 version 17.11 or higher.

# Check your SDK version
dotnet --version
# Should show 8.0.400 or higher

Create a Basic Skill

// Program.cs
using AlexaVoxCraft.MediatR.Lambda;
using AlexaVoxCraft.Model.Response;

return await LambdaHostExtensions.RunAlexaSkill<MySkillFunction, SkillRequest, SkillResponse>();

// Function.cs
public class MySkillFunction : AlexaSkillFunction<SkillRequest, SkillResponse>
{
 protected override void Init(IHostBuilder builder)
 {
 builder
 .UseHandler<LambdaHandler, SkillRequest, SkillResponse>()
 .ConfigureServices((context, services) =>
 {
 // Handlers are automatically discovered and registered at compile time
 services.AddSkillMediator(context.Configuration);
 });
 }
}

// Handler.cs
public class LaunchRequestHandler : IRequestHandler<LaunchRequest>
{
 public bool CanHandle(IHandlerInput handlerInput) =>
 handlerInput.RequestEnvelope.Request is LaunchRequest;

 public async Task<SkillResponse> Handle(IHandlerInput input, CancellationToken cancellationToken)
 {
 return await input.ResponseBuilder
 .Speak("Welcome to my skill!")
 .Reprompt("What would you like to do?")
 .GetResponse(cancellationToken);
 }
}

📖 Documentation

📚 Complete Documentation - Comprehensive guides and examples

Core Components

• Request Handling - MediatR integration and handler patterns
• Source Generation - Compile-time DI registration with C# interceptors
• APL Integration - Rich visual interface development
• Lambda Hosting - AWS Lambda deployment and optimization
• Session Management - State persistence and user data
• Pipeline Behaviors - Cross-cutting concerns and interceptors

Examples

• Complete Examples - Production-ready trivia skill implementation

📁 Project Structure

AlexaVoxCraft/
├── 📂 src/ # Core library packages
│ ├── 📦 AlexaVoxCraft.Model/ # Base Alexa skill models & serialization
│ ├── 📦 AlexaVoxCraft.Model.Apl/ # APL (Alexa Presentation Language) support
│ ├── 📦 AlexaVoxCraft.MediatR/ # MediatR integration & request handling
│ ├── 📦 AlexaVoxCraft.MediatR.Generators/ # Source generator for compile-time DI
│ ├── 📦 AlexaVoxCraft.Lambda/ # Core Lambda abstractions & serialization
│ ├── 📦 AlexaVoxCraft.Lambda.Host/ # Modern minimal API-style Lambda hosting
│ ├── 📦 AlexaVoxCraft.MediatR.Lambda/ # Legacy Lambda hosting (AlexaSkillFunction)
│ ├── 📦 AlexaVoxCraft.Observability/ # OpenTelemetry instrumentation & telemetry
│ └── 📦 AlexaVoxCraft.Smapi/ # Skill Management API (SMAPI) client
│
├── 📂 samples/ # Working example projects
│ ├── 📱 Sample.Skill.Function/ # Basic skill (legacy hosting)
│ ├── 📱 Sample.Host.Function/ # Modern minimal API hosting
│ ├── 📱 Sample.Generated.Function/ # Source-generated DI demonstration
│ └── 📱 Sample.Apl.Function/ # APL skill with visual interfaces
│
├── 📂 test/ # Comprehensive test coverage
│ ├── 🧪 AlexaVoxCraft.Model.Tests/ # Core model & serialization tests
│ ├── 🧪 AlexaVoxCraft.Model.Apl.Tests/ # APL functionality tests
│ ├── 🧪 AlexaVoxCraft.MediatR.Tests/ # MediatR integration tests
│ ├── 🧪 AlexaVoxCraft.MediatR.Lambda.Tests/ # Lambda hosting tests
│ └── 🧪 AlexaVoxCraft.Smapi.Tests/ # SMAPI client tests
│
├── 📂 AlexaVoxCraft.TestKit/ # Testing utilities & AutoFixture support
└── 📂 docs/ # Documentation source

🛠 Core Concepts

Request Handling Pattern

Skills use the MediatR pattern where:

1. Requests implement IRequestHandler<T>
2. Handlers optionally implement ICanHandle for routing logic
3. Pipeline behaviors handle cross-cutting concerns (logging, exceptions)
4. Lambda functions derive from AlexaSkillFunction<TRequest, TResponse>

Package Breakdown

🧪 Testing

AlexaVoxCraft includes comprehensive testing support:

• xUnit v3 with Microsoft.Testing.Platform
• AutoFixture integration for property-based testing
• AwesomeAssertions for fluent assertions
• TestKit with specimen builders and test utilities

⚠️ Error Handling

Implement the IExceptionHandler interface for centralized error handling:

public class GlobalExceptionHandler : IExceptionHandler
{
 public Task<bool> CanHandle(IHandlerInput handlerInput, Exception ex, CancellationToken cancellationToken)
 {
 return Task.FromResult(true); // Handle all exceptions
 }

 public Task<SkillResponse> Handle(IHandlerInput handlerInput, Exception ex, CancellationToken cancellationToken)
 {
 return handlerInput.ResponseBuilder
 .Speak("Sorry, something went wrong. Please try again.")
 .GetResponse(cancellationToken);
 }
}

📋 Version 4.0.0+ Breaking Changes

Cancellation Token Support

Version 4.0.0 introduces cancellation token support for Lambda functions. This is a breaking change that requires updates to your existing lambda handlers.

Required Changes

1. Update Lambda Handlers

Lambda handlers must now accept and pass the cancellation token:

// ❌ Before (v3.x)
public class LambdaHandler : ILambdaHandler<SkillRequest, SkillResponse>
{
 public async Task<SkillResponse> HandleAsync(SkillRequest input, ILambdaContext context)
 {
 return await _skillMediator.Send(input);
 }
}

// ✅ After (v4.0+)
public class LambdaHandler : ILambdaHandler<SkillRequest, SkillResponse>
{
 public async Task<SkillResponse> HandleAsync(SkillRequest input, ILambdaContext context, CancellationToken cancellationToken)
 {
 return await _skillMediator.Send(input, cancellationToken);
 }
}

2. Update AlexaSkillFunction Override

If you override FunctionHandlerAsync in your skill function class, you must update the signature:

// ❌ Before (v3.x)
public class MySkillFunction : AlexaSkillFunction<SkillRequest, SkillResponse>
{
 public override async Task<SkillResponse> FunctionHandlerAsync(SkillRequest input, ILambdaContext context)
 {
 // Custom logic here
 return await base.FunctionHandlerAsync(input, context);
 }
}

// ✅ After (v4.0+)
public class MySkillFunction : AlexaSkillFunction<SkillRequest, SkillResponse>
{
 public override async Task<SkillResponse> FunctionHandlerAsync(SkillRequest input, ILambdaContext context, CancellationToken cancellationToken)
 {
 // Custom logic here
 return await base.FunctionHandlerAsync(input, context, cancellationToken);
 }
}

Configuration Options

You can now configure the cancellation timeout buffer in your appsettings.json:

{
 "SkillConfiguration": {
 "SkillId": "amzn1.ask.skill.your-skill-id",
 "CancellationTimeoutBufferMilliseconds": 500
 }
}

The timeout buffer (default: 250ms) is subtracted from Lambda's remaining execution time to allow graceful shutdown and telemetry flushing.

📋 Version 5.0.0+ Breaking Changes

Overview

Version 5.0.0 introduces a modern minimal API-style hosting model powered by the AwsLambda.Host package. This update also restructures the package architecture to better separate concerns and provide more flexibility. The legacy hosting approach remains fully supported for backward compatibility.

Package Restructuring

Version 5.0.0 introduces two new packages and refactors the existing Lambda hosting:

Namespace Changes

Core Lambda abstractions have been moved to the new AlexaVoxCraft.Lambda package:

Classes Moved:

• ILambdaHandler<TRequest, TResponse>
• HandlerDelegate<TRequest, TResponse>
• AlexaLambdaSerializer
• SystemTextDestructuringPolicy

Removed Obsolete Classes

The following obsolete class has been removed:

PollyVoices - This class was marked as obsolete in previous versions and has been removed. Use the AlexaSupportedVoices class instead for Amazon Polly voice name constants.

Before (v4.x):

using AlexaVoxCraft.MediatR.Lambda.Abstractions;
using AlexaVoxCraft.MediatR.Lambda.Serialization;

public class LambdaHandler : ILambdaHandler<SkillRequest, SkillResponse>
{
 // Implementation
}

After (v5.0+):

using AlexaVoxCraft.Lambda.Abstractions;
using AlexaVoxCraft.Lambda.Serialization;

public class LambdaHandler : ILambdaHandler<SkillRequest, SkillResponse>
{
 // Implementation
}

Two Hosting Approaches

Version 5.0.0 provides two ways to host Alexa skills in AWS Lambda:

🌟 Modern Approach (Recommended for New Projects)

Use AlexaVoxCraft.Lambda.Host for a familiar minimal API-style hosting experience:

dotnet add package AlexaVoxCraft.Lambda.Host

// Program.cs
using AlexaVoxCraft.Lambda.Host;
using AlexaVoxCraft.Lambda.Host.Extensions;
using AwsLambda.Host.Builder;

var builder = LambdaApplication.CreateBuilder();

builder.Services.AddSerilog(/* ... */);
builder.Services.AddSkillMediator(builder.Configuration);
builder.Services.AddAlexaSkillHost<LambdaHandler, SkillRequest, SkillResponse>();

await using var app = builder.Build();
app.MapHandler(AlexaHandler.Invoke<SkillRequest, SkillResponse>);
await app.RunAsync();

Benefits:

• Familiar minimal API-style builder pattern (similar to ASP.NET Core)
• Uses industry-standard AwsLambda.Host package
• More flexible service configuration
• Better separation of concerns

Project Configuration:

<PropertyGroup>
 <InterceptorsNamespaces>$(InterceptorsNamespaces);AwsLambda.Host.Core.Generated</InterceptorsNamespaces>
</PropertyGroup>

Legacy Approach (Existing Projects)

Continue using AlexaVoxCraft.MediatR.Lambda with the AlexaSkillFunction pattern:

dotnet add package AlexaVoxCraft.MediatR.Lambda

// Program.cs
using AlexaVoxCraft.MediatR.Lambda;

return await LambdaHostExtensions.RunAlexaSkill<MySkillFunction, SkillRequest, SkillResponse>();

// Function.cs
public class MySkillFunction : AlexaSkillFunction<SkillRequest, SkillResponse>
{
 protected override void Init(IHostBuilder builder)
 {
 builder
 .UseHandler<LambdaHandler, SkillRequest, SkillResponse>()
 .ConfigureServices((context, services) =>
 {
 services.AddSkillMediator(context.Configuration);
 });
 }
}

This approach remains fully supported and requires no migration for existing projects.

Migration Impact

Who is affected:

• Projects directly referencing AlexaVoxCraft.MediatR.Lambda.Abstractions namespace
• Projects directly referencing AlexaVoxCraft.MediatR.Lambda.Serialization namespace
• Projects wanting to adopt the modern hosting approach

Who is NOT affected:

• Projects using AlexaSkillFunction<TRequest, TResponse> without directly referencing moved classes
• Projects that don't import the moved namespaces

Required Actions for Migration

1. Update Namespace Imports

If you directly reference the moved classes, update your using statements:

// Change this:
using AlexaVoxCraft.MediatR.Lambda.Abstractions;
using AlexaVoxCraft.MediatR.Lambda.Serialization;

// To this:
using AlexaVoxCraft.Lambda.Abstractions;
using AlexaVoxCraft.Lambda.Serialization;

2. (Optional) Migrate to Modern Hosting

To adopt the new minimal API-style hosting:

1. Replace package reference:

   dotnet remove package AlexaVoxCraft.MediatR.Lambda
   dotnet add package AlexaVoxCraft.Lambda.Host
   

2. Update project file to include interceptors:

   <InterceptorsNamespaces>$(InterceptorsNamespaces);AwsLambda.Host.Core.Generated</InterceptorsNamespaces>
   

3. Refactor Program.cs to use builder pattern (see example above)

4. Remove Function class inheriting from AlexaSkillFunction

For detailed migration guidance, see the Lambda Hosting documentation.

🤝 Contributing

PRs are welcome! Please submit issues and ideas to help make this toolkit even better.

📜 Credits & Attribution

📦 Credits:

• Core Alexa skill models (AlexaVoxCraft.Model) based on timheuer/alexa-skills-dotnet
• APL support (AlexaVoxCraft.Model.Apl) based on stoiveyp/Alexa.NET.APL

📜 License

This project is licensed under the .

Stargazers over time