# Remote Development

{% hint style="info" %}
Note that this section requires Docker to be installed locally on your machine. Additionally, you will need the Remote Development extension pack. These extensions are installed as part of the VS Code Can Do That extension pack.
{% endhint %}

Remote development is one of the newest and most exciting features of VS Code. 

Developers have historically struggled against their environments. Code needs a properly configured environment to run, and configuration can be confusing and time consuming. This struggle is replicated whenever a new developer tries to onboard to a library, framework or project.

In this section, you'll learn how to use Remote Development Containers to isolate complex environments and ship them with your code. This allows you and anyone else who wants to work on the code base to instantly get up and running without having to configure their environment.

You will be working in the "exercise-6-remote-development" folder. This project will ask you to open the workspace file. Make sure you select "Open Workspace"

![](/files/-Lm6BpAr3BV4sBZ2xnmi)

You may also see a warning about "Multiple Functions Projects". You can safely ignore this warning and close the notification.

![](/files/-Lm6By1piCqWXkxqoroK)

{% hint style="info" %}
Note that while there is Remote Development for SSH, Containers and WSL, this section of exercises only covers Containers.
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://burkeholland.gitbook.io/vs-code-can-do-that/exercise-6-remote-development/before-you-start.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.