Skip to main content

AWS Lambda adds support for C#

Yesterday I blogged about Azure Functions and how the Visual Studio tooling can make your life easier. But the guys at Amazon are not sleeping and I noticed that they added support for C# as well.

Note that the AWS Lambda functions in C# are using the .NET Core 1.0 runtime. Similar to Microsoft, you get full tooling support thanks to the AWS Toolkit for Visual Studio.

  • Install the AWS Toolkit for Visual Studio.
  • Open Visual Studio and create a new project. Choose the AWS Lambda Project template and click OK.

image

  • Next step is to select a Blueprint.
    • We choose the Simple S3 Function blueprint.

image

  • You get a new project containing the following files
    • aws-lambda-tools-defaults.json: . This file contains default values that the blueprint has set to help prepopulate some of the fields in the deployment wizard.
    • Function.cs: Inside this cs file you can add your own logic.
    • project.json: this is the default project.json for .NET core applications(will be replaced by a csproj file in the near future)

image

  • The SDK is accompagnied by dotnet CLI integration. Open a command prompt and type dotnet lambda. Unfortunately I couldn’t find a way to debug locally.

image

More information at https://aws.amazon.com/blogs/developer/using-the-aws-lambda-project-in-visual-studio/

Labels:

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

VS Code Planning mode

After the introduction of Plan mode in Visual Studio , it now also found its way into VS Code. Planning mode, or as I like to call it 'Hannibal mode', extends GitHub Copilot's Agent Mode capabilities to handle larger, multi-step coding tasks with a structured approach. Instead of jumping straight into code generation, Planning mode creates a detailed execution plan. If you want more details, have a look at my previous post . Putting plan mode into action VS Code takes a different approach compared to Visual Studio when using plan mode. Instead of a configuration setting that you can activate but have limited control over, planning is available as a separate chat mode/agent: I like this approach better than how Visual Studio does it as you have explicit control when plan mode is activated. Instead of immediately diving into execution, the plan agent creates a plan and asks some follow up questions: You can further edit the plan by clicking on ‘Open in Editor’: ...
Read more