Edition 0 Updated to asp. Net core 0

Visual Studio Code and Docker CLI
. If you prefer a lightweight and cross-platform editor that 
supports any development language, you can use Visual Studio Code and the Docker CLI. This IDE is a 
cross-platform development approach for macOS, Linux, and Windows. Additionally, Visual Studio 
Code supports extensions for Docker such as IntelliSense for Dockerfiles and shortcut tasks to run 
Docker commands from the editor. 
By installing 
Docker Desktop
, you can use a single Docker CLI to build apps for both Windows and 
Linux. 

---

73 
CHAPTER 4 | Development process for Docker-based applications 
Additional resources 
•
Visual Studio
. Official site. 
https://visualstudio.microsoft.com/vs/
 
•
Visual Studio Code
. Official site. 
https://code.visualstudio.com/download
 
•
Docker Desktop for Windows
https://hub.docker.com/editions/community/docker-ce-desktop-windows
 
•
Docker Desktop for Mac
https://hub.docker.com/editions/community/docker-ce-desktop-mac
 
.NET languages and frameworks for Docker 
containers 
As mentioned in earlier sections of this guide, you can use .NET Framework, .NET 7, or the open-
source Mono project when developing Docker containerized .NET applications. You can develop in 
C#, F#, or Visual Basic when targeting Linux or Windows Containers, depending on which .NET 
framework is in use. For more details about.NET languages, see the blog post 
The .NET Language 
Strategy
. 
Development workflow for Docker apps 
The application development life cycle starts at your computer, as a developer, where you code the 
application using your preferred language and test it locally. With this workflow, no matter which 
language, framework, and platform you choose, you’re always developing and testing Docker 
containers, but doing so locally. 
Each container (an instance of a Docker image) includes the following components: 
•
An operating system selection, for example, a Linux distribution, Windows Nano Server, or 
Windows Server Core. 
•
Files added during development, for example, source code and application binaries. 
•
Configuration information, such as environment settings and dependencies.