ASP.NET Core is a new open-source and cross-platform framework for building modern cloud-based and internet-connected applications using the C# programming language.
In this lab, you will deploy a simple ASP.NET Core app to App Engine flexible environment. This codelab builds on the Build and launch ASP.NET Core app from Google Cloud Shell codelab. You might want to do that lab first before attempting this lab.
Google App Engine applications are easy to create, maintain, and scale as your traffic and data storage needs change. With App Engine, there are no servers to manage. You simply upload your application and it's ready to go.
App Engine applications automatically scale based on incoming traffic. App Engine natively supports load balancing, microservices, authorization, SQL and NoSQL databases, Memcache, traffic splitting, logging, search, versioning, roll out and roll backs, and security scanning, all of which are highly customizable.
App Engine's environments, the standard environment and the flexible environment, support a host of programming languages, including C#, Java, Python, PHP, Node.js, Go, and more. The two environments give users maximum flexibility in how their application behaves, since each environment has certain strengths. For more information, read Choosing an App Engine Environment.
If you don't already have a Google account (Gmail or G Suite), you must create one. Then, sign-in to Google Cloud Platform console (console.cloud.google.com) and create a new project:
Remember the project ID (which is different from the project name), a unique name across all Google Cloud Platform projects. It will be referred to later in this codelab as
Next, you'll need to enable billing in Google Cloud Console in order to use Google Cloud Platform resources.
From Google Cloud Platform Console, click on the "Activate Google Cloud Shell" icon in the top right hand corner of the header bar.
A Cloud Shell session opens inside a new frame at the bottom of the console and displays a command-line prompt. This might take a few seconds as Cloud Shell is spinning up a VM.
Wait until the $ prompt appears.
In Cloud Shell prompt, dotnet command line tool is already installed and you can verify its version as follows.
Next, create a new skeleton ASP.NET Core web app.
dotnet new razor -o HelloWorldAspNetCore
This should create a project and restore its dependencies. You should see a message similar to below.
Restore completed in 11.44 sec for HelloWorldAspNetCore.csproj. Restore succeeded.
We're almost ready to run our app. Navigate to the app folder.
Finally, run the app.
Application starts listening on port 8080.
Hosting environment: Production Content root path: /home/atameldev/HelloWorldAspNetCore Now listening on: http://[::]:8080 Application started. Press Ctrl+C to shut down.
To verify that the app is running, click on the web preview button on the top right and select ‘Preview on port 8080'.
You'll see the default ASP.NET Core webpage which simply prints Hello World in a new tab.
Now, publish the app to get a self-contained DLL using the
dotnet publish command.
dotnet publish -c Release
publish displays some messages with a successfully published DLL at the end of the process.
... HelloWorldAspNetCore -> /home/atameldev/HelloWorldAspNetCore/bin/Release/netcoreapp1.1/HelloWorldAspNetCore.dll
Navigate to the the publish folder for the next step.
app.yaml file describes how to deploy the app to App Engine, in this case, the App Engine flexible environment. Create an
app.yaml file inside
Edit the generated
app.yaml file and specify the environment as flex and runtim as aspnetcore.
env: flex runtime: aspnetcore
Once you've saved the
app.yaml file to the
publish directory, you're ready to deploy your app to App Engine flexible using
gcloud. Just follow the prompts to create an App Engine application.
gcloud beta app deploy --version v0
During deployment, you will be asked to choose a region for your application. Chose a region where you want your app to run in.
Please choose a region for your application. After choosing a region, you cannot change it. Which region would you like to choose?  europe-west (supports standard and flexible)  us-central (supports standard and flexible)  us-east1 (supports standard and flexible)  asia-northeast1 (supports standard and flexible)  cancel
This will create an image for your application in the cloud, save that image to Google Container Registry and deploy to App Engine. In the end, you should see that the app is deployed.
... Deployed service [default] to [https://<project-id>.appspot.com]
After you've deployed the application,visit it by opening the URL
http://<project-id>.appspot.com in your web browser.
You'll see the default ASP.NET Core webpage in a new tab.
At some point, the application that you've deployed to production will require bug fixes or additional features. App Engine is here to help you deploy a new version to production without impacting your users.
First, let's modify the application. Open the code editor from Cloud Shell.
Pages folder of
HelloWorldAspNetCore and update one of the default messages:
Learn how to build ASP.NET apps that can run anywhere.
And change it to this.
Learn how to build ASP.NET apps that can run on Google Cloud!
Save the changes and then go back to Cloud Shell. Inside
HelloWorldAspNetCore,publish the app to get a self-contained DLL.
dotnet publish -c Release
Navigate to the publish directory.
You can now deploy a new version of your app (
v2 in this case).
gcloud beta app deploy --version v2
Once it's deployed, you can go to App Engine versions section of Google Cloud Console to see the new version of your app serving all of the traffic with the new message.
It's time to shutdown the app to save on cost and to be an overall good cloud citizen.
Go to the versions section of App Engine.
Select the version and stop it.
Once the version is stopped, the backing instances will be deleted and you should see instance count to drop down to zero.
There! You've created an ASP.NET Core app, packaged it as a Docker container, and deployed it to Google App Engine Flexible.
This work is licensed under a Creative Commons Attribution 2.0 Generic License.