Try Out Development Containers: .NET

A development container is a running container with a well-defined tool/runtime stack and its prerequisites. You can try out development containers with GitHub Codespaces or Visual Studio Code Dev Containers.

This is a sample project that lets you try out either option in a few easy steps. We have a variety of other vscode-remote-try-* sample projects, too.

Note: If you already have a Codespace or dev container, you can jump to the Things to try section.

Setting up the development container

GitHub Codespaces

Follow these steps to open this sample in a Codespace:

1. Click the Code drop-down menu.
2. Click on the Codespaces tab.
3. Click Create codespace on main .

For more info, check out the GitHub documentation.

VS Code Dev Containers

If you already have VS Code and Docker installed, you can click the badge above or here to get started. Clicking these links will cause VS Code to automatically install the Dev Containers extension if needed, clone the source code into a container volume, and spin up a dev container for use.

Follow these steps to open this sample in a container using the VS Code Dev Containers extension:

1. If this is your first time using a development container, please ensure your system meets the pre-reqs (i.e. have Docker installed) in the getting started steps.

2. To use this repository, you can either open the repository in an isolated Docker volume:

   • Press F1 and select the Dev Containers: Try a Sample... command.
   • Choose the ".NET Core" sample, wait for the container to start, and try things out!

     Note: Under the hood, this will use the Dev Containers: Clone Repository in Container Volume... command to clone the source code in a Docker volume instead of the local filesystem. Volumes are the preferred mechanism for persisting container data.

   Or open a locally cloned copy of the code:

   • Clone this repository to your local filesystem.
   • Press F1 and select the Dev Containers: Open Folder in Container... command.
   • Select the cloned copy of this folder, wait for the container to start, and try things out!

3. If you want to enable HTTPS, see enabling HTTPS to reuse your local development cert in the container.

Things to try

Once you have this sample opened, you'll be able to work with it like you would locally.

Some things to try:

1. Restore Packages: When notified by the C# extension to install packages, click Restore to trigger the process from inside the container! You can also execute dotnet restore command in a terminal.

2. Edit:

   • Open Program.cs
   • Try adding some code and check out the language features.
   • Make a spelling mistake and notice it is detected. The Code Spell Checker extension was automatically installed because it is referenced in .devcontainer/devcontainer.json.
   • Also notice that the C# extension is installed. Tools are installed in the mcr.microsoft.com/devcontainers/dotnet image and Dev Container settings and metadata are automatically picked up from image labels.

3. Build, Run, and Debug:

   • Open Program.cs
   • Add a breakpoint (e.g. on line 16).
   • Press F5 to launch the app in the container.
   • Navigate to the weather endpoint, for example, http://localhost:5000/paris/weather.
   • Once the breakpoint is hit, try hovering over variables, examining locals, and more.
   • Continue (F5). You can connect to the server in the container by either:
     • Clicking on Open in Browser in the notification telling you: Your service running on port 5000 is available.
     • Clicking the globe icon in the 'Ports' view. The 'Ports' view gives you an organized table of your forwarded ports, and you can access it with the command Ports: Focus on Ports View.
   • Notice port 5000 in the 'Ports' view is labeled "Hello Remote World." In devcontainer.json, you can set "portsAttributes", such as a label for your forwarded ports and the action to be taken when the port is autoforwarded.

   Note: In Dev Containers, you can access your app at http://localhost:5000 in a local browser. But in a browser-based Codespace, you must click the link from the notification or the Ports view so that the service handles port forwarding in the browser and generates the correct URL.

4. Rebuild or update your container

   You may want to make changes to your container, such as installing a different version of a software or forwarding a new port. You'll rebuild your container for your changes to take effect.

   Open browser automatically: As an example change, let's update the portsAttributes in the .devcontainer/devcontainer.json file to open a browser when our port is automatically forwarded.

   • Open the .devcontainer/devcontainer.json file.
   • Modify the "onAutoForward" attribute in your portsAttributes from "notify" to "openBrowser".
   • Press F1 and select the Dev Containers: Rebuild Container or Codespaces: Rebuild Container command so the modifications are picked up.

5. Install Node.js using a Dev Container Feature:

   • Press F1 and select the Dev Containers: Configure Container Features... or Codespaces: Configure Container Features... command.
   • Type "node" in the text box at the top.
   • Check the check box next to "Node.js (via nvm) and yarn" (published by devcontainers)
   • Click OK
   • Press F1 and select the Dev Containers: Rebuild Container or Codespaces: Rebuild Container command so the modifications are picked up.

Contributing

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.

When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.

Trademarks

This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or logos is subject to and must follow Microsoft's Trademark & Brand Guidelines. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. Any use of third-party trademarks or logos are subject to those third-party's policies.