Exercise - Write code to implement a web application

100 XP

5 minutes

This module requires a sandbox to complete. A sandbox gives you access to free resources. Your personal subscription will not be charged. The sandbox may only be used to complete training on Microsoft Learn. Use for any other reason is prohibited, and may result in permanent loss of access to the sandbox.

Microsoft provides this lab experience and related content for educational purposes. All presented information is owned by Microsoft and intended solely for learning about the covered products and services in this Microsoft Learn module.

In this unit, you use developer tools to create the code for a starter web application.

Create a new web project

The heart of the .NET CLI tools is the dotnet command-line tool. Using this command, you create a new ASP.NET Core web project.

Run the following command to create a new ASP.NET Core Model-View Cotroller (MVC) application named "BestBikeApp":

Bash

dotnet new mvc --name BestBikeApp

The command creates a new folder named "BestBikeApp" to hold your project.

Optionally test your web app

You can test your application locally on Azure. To do so, use the following steps:

Run the following commands to build and run your web application in the background:

Bash

cd BestBikeApp
dotnet run &

You should get output like the following example:

Console

[1] <process-number>
<username> [ ~/BestBikeApp ]$ Building...
warn: Microsoft.AspNetCore.DataProtection.KeyManagement.XmlKeyManager[35]
      No XML encryptor configured. Key {b4a2970c-215c-4eb2-92b4-c28d021158c6} may be persisted to storage in unencrypted form.
info: Microsoft.Hosting.Lifetime[14]
      Now listening on: http://localhost:<port>
info: Microsoft.Hosting.Lifetime[0]
      Application started. Press Ctrl+C to shut down.
info: Microsoft.Hosting.Lifetime[0]
      Hosting environment: Development
info: Microsoft.Hosting.Lifetime[0]
      Content root path: /home/cephas_lin/BestBikeApp

In the output, take note of the values of <process-number> and <port>.

Run the following command to browse to your web application, replacing <port> with the port you noted in the last step.

Bash

curl -kL http://localhost:<port>/

You should see some HTML appear, ending in the following lines:

HTML

<div class="text-center">
    <h1 class="display-4">Welcome</h1>
    <p>Learn about <a href="https://learn.microsoft.com/aspnet/core">building Web apps with ASP.NET Core</a>.</p>
</div>

        </main>
    </div>

    <footer b-b5g3qljvtd class="border-top footer text-muted">
        <div b-b5g3qljvtd class="container">
            &copy; 2024 - BestBikeApp - <a href="/Home/Privacy">Privacy</a>
        </div>
    </footer>
    <script src="/lib/jquery/dist/jquery.min.js"></script>
    <script src="/lib/bootstrap/dist/js/bootstrap.bundle.min.js"></script>
    <script src="/js/site.js?v=hRQyftXiu1lLX2P9Ly9xa4gHJgLeR1uGN5qegUobtGo"></script>

</body>
</html>

Using <process-number> that you noted earlier, stop dotnet:

Azure CLI
```
kill <process-number>
```

To create a starter web application, we use Maven, a commonly used project-management and build tool for Java apps. We use the maven-archetype-webapp template to generate the code for our web application.

Run the following commands in Azure Cloud Shell now to create a new web app:

Bash

cd ~
mvn archetype:generate -DgroupId=example.demo -DartifactId=helloworld -DinteractiveMode=false -DarchetypeArtifactId=maven-archetype-webapp -DarchetypeVersion=1.5

Now, run these commands to change to the new "helloworld" application directory and package the application for deployment:

Bash
```
cd helloworld
mvn package
```
When the command finishes running, run these commands to open the target directory and list its content:

Bash
```
cd target
ls
```

You now have a file called helloworld.war that's the web application package we're going to deploy to App Service.

To create a starter Node.js web application, we use Node Package Manager (npm) along with some JavaScript code to run the actual web page processing.

Run the following commands in the terminal to create a new package.json file that describes our Node.js application:

Bash

cd ~
mkdir helloworld
cd helloworld
cat >package.json <<EOL
{
  "name": "helloworld",
  "version": "1.0.0",
  "scripts": {
    "start": "node index.js"
  }
}
EOL

A new package.json file is created in the current folder. You should find it in the current folder if you enter ls in the terminal window. We need a JavaScript file to run our website logic. For this basic example, we only need one file: index.js.

Create the file by running the following command in the terminal:

Bash

cat >index.js <<EOL
const http = require('http');

const server = http.createServer(function(request, response) { 
    response.writeHead(200, { "Content-Type": "text/html" });
    response.end("<html><body><h1>Hello World!</h1></body></html>");
});

const port = process.env.PORT || 1337;
server.listen(port);

console.log(\`Server running at http://localhost:\${port}\`);
EOL

Optionally test your web app

While you're running the helloworld web app, you can verify it's running locally by opening a second command shell session.

From a new browser tab, browse to https://shell.azure.com/.
From your primary command shell session, run the following commands to start your web application in the background:

Bash
```
cd ~/helloworld
npm start &
```
You should get output like the following example:

Console
```
[1] <process-number>
> helloworld@1.0.0 start
> node index.js

Server running at http://localhost:1337
```
In the output, take note of the value of <process-number>.
In the same Cloud Shell session, run the following command to browse to your web application.

Bash
```
curl -kL http://localhost:1337/
```
You should get the following output:

HTML
```
<html><body><h1>Hello World!</h1></body></html>
```
Using <process-number> that you noted earlier, stop node:

Azure CLI
```
kill <process-number>
```

To create a starter web application, we use the Flask web-application framework.

Run the following commands in Azure Cloud Shell to set up a virtual environment and install Flask in your profile:

Bash
```
python3 -m venv venv
source venv/bin/activate
pip install flask
```
Run these commands to create and switch to your new web app directory:

Bash
```
mkdir ~/BestBikeApp
cd ~/BestBikeApp
```

Create a new file called application.py with a basic HTML response:

Bash

cat >application.py <<EOL
from flask import Flask
app = Flask(__name__)

@app.route("/")
def hello():
    return "<html><body><h1>Hello Best Bike App!</h1></body></html>\n"
EOL

To deploy your application to Azure, you need to save the list of application requirements you made for it in a requirements.txt file. To do so, run the following command:

Bash
```
pip freeze > requirements.txt
```

Optionally test your web app

You can test your application locally in Azure while it's running.

Run the following commands to start your web application in the background:

Bash
```
cd ~/BestBikeApp
export FLASK_APP=application.py
flask run &
```
You should get output like the following example:

Console
```
[1] <process-number>
 * Serving Flask app 'application.py'
 * Debug mode: off
WARNING: This is a development server. Do not use it in a production deployment. Use a production WSGI server instead.
 * Running on http://127.0.0.1:5000
Press CTRL+C to quit
```
In the output, take note of the value of <process-number>. Since the process is running in the background, you can't quit with CTRL+C. You'll need to stop it with its process number.
Run the following command to browse to your web application.

Bash
```
curl -kL http://localhost:5000/
```
You should get the following HTML output:

HTML
```
<html><body><h1>Hello Best Bike App!</h1></body></html>
```
Using <process-number> that you noted earlier, stop Flask:

Azure CLI
```
kill <process-number>
```

Next unit: Deploy code to App Service

Previous Next

Having an issue? We can help!

For issues related to this module, explore existing questions using the #azure training tag or Ask a question on Microsoft Q&A.
For issues related to Certifications and Exams, post on Certifications Support Forums or visit our Credentials Help.

Create a new web project

Optionally test your web app

Optionally test your web app

Optionally test your web app

Next unit: Deploy code to App Service

Feedback

Ask Learn