Folder Structure

LambdaSharp modules must follow a consistent folder organization. The root folder must contain the Module.yml file. Each function listed in the Module.yml must have a corresponding folder the naming convention {FunctionName}. The .NET Core projects file (.csproj) for each function must be contained within the sub-folder and be named with the same naming convention. (e.g. {FunctionName}.csproj).

• GettingStarted
  • Module.yml
  • SlackCommand
    • SlackCommand.csproj

Furthermore, the project file should contain the <RootNamespace> element to define the root namespace of the project. When missing, the function configuration will need to explicitly list the name of the function handler using the Handler setting.

<Project Sdk="Microsoft.NET.Sdk">
  <PropertyGroup>
    <TargetFramework>netcoreapp3.1</TargetFramework>
    <Deterministic>true</Deterministic>
    <GenerateRuntimeConfigurationFiles>true</GenerateRuntimeConfigurationFiles>
    <RootNamespace>GettingStarted.SlackCommand</RootNamespace>
  </PropertyGroup>
</Project>

Furthermore, the function handler should be in a class called Function and the method should be called FunctionHandler. When different, the function configuration will need to explicitly list the name of the function handler using the Handler setting.

In order for the LambdaSharp CLI to work properly the .NET Core project file must contain a reference to Amazon.Lambda.Tools.

namespace GettingStarted.SlackCommand {

    public sealed class Function : ALambdaSlackCommandFunction {

        // ...implementation code...
    }
}