Updated 03. Setting the eShopOnContainers solution up in a Windows CLI environment (dotnet CLI, Docker CLI and VS Code) (markdown)

Cesar De la Torre 2017-10-27 11:11:14 -07:00
parent 84f4bdc405
commit 3d6b2d0275

@ -24,13 +24,16 @@ This CLI environment means that you want to build/run by using the CLI (Command
You don't need Visual Studio 2017 for this environment but can use any code editor like Visual Studio Code, Sublime, etc. Of course, you could still use VS 2017 at the same time, as well.
## Prerequisites
## Prerequisites (Software requirements)
1. [Docker for Windows](https://docs.docker.com/docker-for-windows/install/).
1. [Docker for Windows](https://docs.docker.com/docker-for-windows/install/). Important, follow the concrete configuration specified in the steps below.
1. A Git client. The [git-scm site](https://git-scm.com/download/gui/mac) maintains a great list of clients.
1. [Node.js](http://nodejs.org). The stable channel is fine as well.
1. Bower (/> npm install -g bower) needed for the MVC web app.
1. [.NET Core and SDK](http://dot.net). Install the SDK and runtime.
1. Any code editor, like [Visual Studio Code](https://code.visualstudio.com/)
*IMPORTANT NOTE:* When building with the Linux build-container (option A explained below) you don't really need to have installed Node. NPM, Bower or not even .NET Core SDK in your local Windows machine, as the Linux build-container has all the needed SDK to compile. However, we recommend to have it installed on Windows so you can do further development and testing, better.
# Setting up the development environment
@ -137,19 +140,7 @@ The recommended approach is to build the .NET bits and Docker images by using an
The build container to use is based on the `image: microsoft/aspnetcore-build` ASP.NET Core build image which includes the .NET SDK, NPM and many other Web and ASP.NET dependencies (Gulp, Bower, etc.) to build your services and web apps.
See building procedure below.
### Software requirements
Software installation requirements for a Windows dev machine with CLI SDKs, "Docker for Windows" and Visual Studio Code or any other editor.
WINDOWS DEV MACHINE
- <a href='https://docs.docker.com/docker-for-windows/install/'>Docker for Windows</a>. Important, follow the concrete configuration specified in the steps below.
- <a href='https://git-for-windows.github.io/'>Git for Windows</a>. Have your preferred way to install and have available the git command line tool. Either <a href='https://git-for-windows.github.io/'>Git for Windows</a> or <a href='https://desktop.github.com/'>Git for Desktop</a> can also work.
- <a href='https://www.microsoft.com/net/download/core#/current'>.NET Core SDK</a> - Latest version. As of early March 2017, using .NET 1.1 SDK. Note that this requirement is optional because when building through the "build container" it will be using the .NET SDK available within the ASPNETCore build image, not the local .NET Core SDK. However, it is recommended to have it installed locally for any further building/testing of the ASP.NET Core projects without Docker.
- <a href='https://code.visualstudio.com/'>Visual Studio Code</a> or any other code editor.
- NPM and related dependencies for running the SPA Web app. <a href='https://github.com/dotnet/eShopOnContainers/wiki/06.-Setting-the-Web-SPA-application-up'>SPA app setup process described here. </a>
## Build the bits through the build container image
## Build the bits through the Linux build-container image
This step is very much simplified thanks to the mentioned compilation process based on a build-container using the image `image: microsoft/aspnetcore-build:1.0-1.1` ASP.NET Core build image which includes the .NET SDK, NPM and many other Web and ASP.NET dependencies (Gulp, Bower, etc.) to build your services and web apps.