ContentCon is almost full! Reserve your spot in Austin on 5/23

Join us at ContentCon
Register Now

Build a Starter Website Using ASP.NET Blazor and Contentstack .NET SDK

Blazor is a feature of ASP.NET, a popular web development framework that extends the .NET developer platform with tools and libraries for building web apps.

This guide will help you create a starter marketing website using Blazor with minimal steps. It uses Contentstack .NET SDK to store and deliver the website content from Contentstack.

Screenshots

homepage.png
about-us.png

Prerequisites

Note: For this tutorial, we have assumed that you are familiar with Contentstack and ASP.NET Blazor. If not, please refer to the Contentstack docs and ASP.Net Blazor for more details.

Set Up Your App

Here is an overview of the steps involved in creating our .Net app:

  1. Set the Region
  2. Login to your Account
  3. Import Content using Seed Command
  4. Create Delivery Token
  5. Build and Configure the Website
  6. Deploy the Website
  1. Set the Region

    Note: By default, the CLI uses the North America endpoint. Configuration changes are not required for North American region users.

    To use the European or Azure North American endpoint, run the following command in your terminal (command prompt):

    csdx config:set:region <<region>> 
    

    Note: For European users set region as EU.
    Azure North American users set region as AZURE-NA.

  2. Login to your Account

    To import content to your stack, first, you’ll need to log in to your Contentstack account via CLI by running the following command in your terminal:

    csdx auth:login
    

    This command will ask you to provide your Contentstack’s account credentials (email and password).

  3. Import Content

    The ‘seed’ command lets you import content to your stack in a few steps. To do so, run the following command in your terminal:

    csdx cm:seed -r "contentstack/stack-starter-app"
    

    This command will prompt the following options as follows:

    • Organization name: You’ll get a list of organizations to which you have access. Select the one from the list where your source stack is located or where you want to create a new stack.
    • Stack preference:

      Next, you need to select your choice to create a new stack:

      • If you select Yes, you’ll receive a list of organizations to which you belong. Then, choose an organization where you are either an owner or admin to create the new stack, and then enter a name for your stack.
      • If you select No, you need to choose the organization where the destination stack exists and select that particular stack where you have the specific permissions for importing content. Refer to the Stack Roles documentation to learn more about permissions.

    Tip: To avoid the chances of any error, we recommend that you select the option of creating a new destination stack. If you choose to import content to an existing stack, ensure that the stack is empty.

    Finally, you’ll get the content imported to your stack.

  4. Create Delivery Token

    A delivery token lets you fetch published content of an environment.

    You can create a delivery token for the “development” environment for running the website on localhost. Later, while deploying your site, you can create tokens for other environments.

  5. Build and Configure the Website

    Download the website code.

    Navigate to the root folder, create a configuration file named appsettings.json and provide your credentials:

    Note: The below code is for North America region users only. Refer the configuration code for European region and Azure North American region on the regions configuration page.

    {
      "ContentstackOptions": {
        "Host": "cdn.contentstack.io",
        "ApiKey": "<API_KEY>",
        "DeliveryToken": "<DELIVERY_TOKEN>",
        "Environment": "<ENVIRONMENT_NAME>"
      }
    }
    

    Note: Use ASP.NET version 5.0 for sample application.

    That’s it! Now that we have a working project ready, you can build and run it.

    You can now view the website at http://localhost:5000 or http://localhost:5001. And you also have the stack that has all the content and resources for the website. Try experimenting by creating new entries and publishing on the “development” environment. You should be able to see the changes on the website at the localhost.

  6. Deploy the Website

    The easiest and the quickest way to deploy a .NET starter website on production is to use Heroku. You need a Heroku account before you start deploying.

    Perform the following set of steps to deploy your app:

    1. Log in to Container Registry

      First, you must have Docker set up locally to continue:

      $ docker ps
      

      Next, log in to the Container Registry:

      $ heroku container:login
      
    2. Push your Docker-based app

      Build the Dockerfile in the current directory and push the Docker image.

      $ heroku container:push -a <your_application_name> web
      
    3. Deploy the changes

      Release the newly pushed images to deploy your app.

      $ heroku container:release -a <your_application_name> web
      

Was this article helpful?

Thanks for your feedbackSmile-icon

On This Page

^