 Codespaces are anchored around the repository. Here we're using the ASP.NET Core sample web application called eShopOnWeb. With a Codespace, you can select the compute that you want specific to the scale and size of the application you're building. So you can select lower compute to save costs for smaller workloads and higher compute for larger workloads to accelerate your development. Development of Codespaces familiar and consistent with the inner loop of development on a local environment. Here we're building the application to get started and see this simple application running inside of a Codespace. While the UI is rendering locally for Visual Studio, all the heavy lifting is being done inside of the Codespace. For example, the build, debug, and running of this application is all executing in the remote environment. So no local resources are being consumed for those heavy lifting operations. Codespaces include all the dependencies from modern workloads like ASP.NET Core web application development, .NET Core, CMake, and C++ console application. Features that developers use day to day are available inside of a Codespace. Here we're navigating the source code to find a file in order to be able to set a break point. Once we hit our break point, we can step through our source code, inspect variables, and navigate the call stack. Codespaces allow you to not only scale vertically for more compute, but also horizontally to use more resources as you paralyze your work. Here in the background, I have several other instances of Visual Studio running connected to other Codespaces. The Orchard Core sample here is 160 project application, and here the OpenCV CMake application has over 1,500 projects in it. Visual Studio here is building those solutions in parallel while I'm debugging the eShopOnWeb application all at the same time. Switching over to Task Manager, we can see that the CPU on the local machine is staying fairly steady, with most of the resources you see here being consumed in order to record this video rather than actually running all the local instances of Visual Studio.