Skip to main content

How to get started with .Net Core and Lambda functions?

 Recently I started experimenting with .Net Core and AWS Lambda functions, I thought I will share the steps I took to get started

Tools to install

  1. .Net Core 3.1 - https://dotnet.microsoft.com/download/dotnet-core/3.1
  2. AWS CLI - https://aws.amazon.com/cli/ 
  3. AWS Account - 12 months Free Tier - https://aws.amazon.com/free
  4. Terminal - on iOS I use iTerm2 - https://www.iterm2.com 
Once you installed the above tools, head to AWS console and login with your root account to create an account which will be used by AWS CLI. Please see steps here 

Now you can configure AWS CLI as detailed here. Verify that you able to connect to AWS service using CLI.

To make life little easy with dotnet core and Lambda functions, you need to install AWS Extensions nuget pack for .Net CLI

dotnet tool install -g Amazon.Lambda.Tools
You can also install templates to get started quickly 

dotnet new -i Amazon.Lambda.Templates

That's it. Now the fun part!!! 

Create a new project

  1. In terminal window, check the templates installed.
dotnet new help
Pick a template for Lambda functions. For this example I have used serverless.AspNetCoreWebAPI

dotnet new serverless.AspNetCoreWebAPI -n SampleApp
This will create a new app under SampleApp folder. Navigate to SampleApp/src/SampleApp folder and build the app

dotnet build
Now run the app locally

dotnet run
This will start you .Net API running locally. The magic is happening in LocalEntryPoint.cs file which is like your Program.cs which contains the main method and which bootstraps your api. Now you can test your api on localhost:5000 or 5001

If you get error while testing on https port, use this command 

dotnet dev-certs https --trust
You can view detailed article about this issue from Scott Hanselman.

In the next post we will look at how to deploy Lambda function in your AWS account. 


    Labels:

    Comments

    Post a Comment

    Popular posts from this blog

    How to detect HTML5 support for a browser?

    HTML5 has introduced lots of new cool  tags . Not all the browsers support all tags and also the implementation of these tags may be different for each browser. HTML5 specification defines the functional aspects of these tags and not the implementation. Also the general concensus is that by 2022 all browsers will support all new features of HTML5. Of all the modern browsers, Chrome seems to have implemented most, if not all, featutes of HTML5. IE9 supports few. Firefox sits in between. So as a developer how do you make use of the cool HTML5 features without causing any compatibility issues with existing browsers? Traditionally developers have used User Agent to detect browser type and use the features accordingly. However these days, you can easily change a User Agent by using addons in your browser. So you need a more robust way to detect the features supported by the browser as the same engine of two different versions of a browser mig...
    Post a Comment
    Read more

    Searching Unicode characters in Oracle table

    Oracle implementation of Regular expression has no support for using hexadecimal code to search for Unicode characters. The only way to search for Unicode character is it use the character itself. Normally with Regular expression, you can use \x or \u followed by hexadecimal code to search for any character. E.g. \x20 will match space. But REGEXP_LIKE in Oracle does not support \x. You need to use unistr function to convert the code to equivalent character and then use it with REGEXP_LIKE. E.g. REGEXP_LIKE(source,'[' ||unistr('\0020')|| ']');
    Post a Comment
    Read more

    System.Configuration in .Net Framework 2 onwards

    Often application need custom configuration section. System.Configuration namespace includes classes for reading and writing configuration settings. There is a slight difference in how you use this namespace depending on the Framework version you are using Prior to .Net Framework 2.0, the .Net Framework included System.Configuration namespace, but that version of the namespace is now outdated. If you simply add the System.configuration namespace to your project (using in C#), your application references the outdated namespace. To refer to the updated namespace, follow these steps 1. In VS, open the project that requires System.Configuration namespace. 2. Click on the Project menu and then click Add Reference 3. On the .Net tab, Select System.Configuration as shown in following figure, and click OK 4. Now add the System.Configuration namespace to your project normally using Imports (in VB) or using (in C#) and your application will reference the correct version of the namespa...
    Post a Comment
    Read more