Skip to content

Latest commit

 

History

History
132 lines (84 loc) · 6.19 KB

get-started-netcore.md

File metadata and controls

132 lines (84 loc) · 6.19 KB
title titleSuffix services ms.service ms.component author ms.author ms.date ms.topic description keywords manager
Create a Kubernetes dev space in the cloud using .NET Core and VS Code| Microsoft Docs
Azure Dev Spaces
azure-dev-spaces
azure-dev-spaces
azds-kubernetes
ghogen
ghogen
07/09/2018
tutorial
Rapid Kubernetes development with containers and microservices on Azure
Docker, Kubernetes, Azure, AKS, Azure Kubernetes Service, containers
douge

Get Started on Azure Dev Spaces with .NET Core

[!INCLUDE]

[!INCLUDE]

You're now ready to create a Kubernetes-based dev space in Azure.

[!INCLUDE]

Install the Azure CLI

Azure Dev Spaces requires minimal local machine setup. Most of your dev space's configuration gets stored in the cloud, and is shareable with other users. Your local machine can run Windows, Mac, or Linux. For Linux, the following distributions are supported: Ubuntu (18.04, 16.04, and 14.04), Debian 8 and 9, RHEL 7, Fedora 26+, CentOS 7, openSUSE 42.2, and SLES 12.

Start by downloading and running the Azure CLI.

Important

If you already have the Azure CLI installed, make sure you are using version 2.0.43 or higher.

[!INCLUDE]

[!INCLUDE]

[!INCLUDE]

While you're waiting for the cluster to be created, you can start developing code.

Create a web app running in a container

In this section, you'll create a ASP.NET Core web app and get it running in a container in Kubernetes.

Create an ASP.NET Core web app

If you have .NET Core installed, you can quickly create an ASP.NET Core Web App in a folder named webfrontend.

dotnet new mvc --name webfrontend

Or, download sample code from GitHub by navigating to https://github.com/Azure/dev-spaces and select Clone or Download to download the GitHub repository to your local environment. The code for this guide is in samples/dotnetcore/getting-started/webfrontend.

[!INCLUDE]

[!INCLUDE]

Update a content file

Azure Dev Spaces isn't just about getting code running in Kubernetes - it's about enabling you to quickly and iteratively see your code changes take effect in a Kubernetes environment in the cloud.

  1. Locate the file ./Views/Home/Index.cshtml and make an edit to the HTML. For example, change line 70 that reads <h2>Application uses</h2> to something like: <h2>Hello k8s in Azure!</h2>
  2. Save the file. Moments later, in the Terminal window you'll see a message saying a file in the running container was updated.
  3. Go to your browser and refresh the page. You should see the web page display the updated HTML.

What happened? Edits to content files, like HTML and CSS, don't require recompilation in a .NET Core web app, so an active azds up command automatically syncs any modified content files into the running container in Azure, so you can see your content edits right away.

Update a code file

Updating code files requires a little more work, because a .NET Core app needs to rebuild and produce updated application binaries.

  1. In the terminal window, press Ctrl+C (to stop azds up).
  2. Open the code file named Controllers/HomeController.cs, and edit the message that the About page will display: ViewData["Message"] = "Your application description page.";
  3. Save the file.
  4. Run azds up in the terminal window.

This command rebuilds the container image and redeploys the Helm chart. To see your code changes take effect in the running application, go to the About menu in the web app.

But there is an even faster method for developing code, which you'll explore in the next section.

Debug a container in Kubernetes

[!INCLUDE]

[!INCLUDE]

Select the AZDS debug configuration

  1. To open the Debug view, click on the Debug icon in the Activity Bar on the side of VS Code.
  2. Select .NET Core Launch (AZDS) as the active debug configuration.

Note

If you don't see any Azure Dev Spaces commands in the Command Palette, ensure you have installed the VS Code extension for Azure Dev Spaces. Be sure the workspace you opened in VS Code is the folder that contains azds.yaml.

Debug the container in Kubernetes

Hit F5 to debug your code in Kubernetes.

As with the up command, code is synced to the dev space, and a container is built and deployed to Kubernetes. This time, of course, the debugger is attached to the remote container.

[!INCLUDE]

Set a breakpoint in a server-side code file, for example within the Index() function in the Controllers/HomeController.cs source file. Refreshing the browser page causes the breakpoint to hit.

You have full access to debug information just like you would if the code was executing locally, such as the call stack, local variables, exception information, etc.

Edit code and refresh

With the debugger active, make a code edit. For example, modify the About page's message in Controllers/HomeController.cs.

public IActionResult About()
{
    ViewData["Message"] = "My custom message in the About page.";
    return View();
}

Save the file, and in the Debug actions pane, click the Refresh button.

Instead of rebuilding and redeploying a new container image each time code edits are made, which will often take considerable time, Azure Dev Spaces will incrementally recompile code within the existing container to provide a faster edit/debug loop.

Refresh the web app in the browser, and go to the About page. You should see your custom message appear in the UI.

Now you have a method for rapidly iterating on code and debugging directly in Kubernetes! Next, you'll see how you can create and call a second container.

Next steps

[!div class="nextstepaction"] Learn about team development