- Production-Ready Cloud application with Resilient microservices' design and implementation
- Gracefully stopping or shutting down microservice instances - Implemented as an ASP.NET Core middleware in the ASP.NET Core pipeline. Drain in-flight requests before stopping the microservice/container process.
- Implement messaging communication to ensure Commands/Updates' communication success, using queues, etc. plus providing better scalability capabilities.
diff --git a/02.-Setting-eShopOnContainer-solution-up-in-a-Visual-Studio-2017-environment.md b/02.-Setting-eShopOnContainer-solution-up-in-a-Visual-Studio-2017-environment.md
deleted file mode 100644
index eb84198..0000000
--- a/02.-Setting-eShopOnContainer-solution-up-in-a-Visual-Studio-2017-environment.md
+++ /dev/null
@@ -1,236 +0,0 @@
-## Want to try it out from Visual Studio 2017?
-
-Main steps:
-
-```
-- Git clone https://github.com/dotnet/eShopOnContainers.git
-- Open solution eShopOnContainers-ServicesAndWebApps.sln
-- Hit F5!
-```
-NOTE: In order for the authentication based on the STS (Security Token Service) to properly work and have access from remote client apps like the Xamarin mobile app, you also need to open the ports in your firewall as specified in the procedure below.
-For further instructions, especially if this is the first time you are going to try .NET Core on Docker, see the detailed instructions below. Also **you'll need it the first time in order to make the SPA (Single Page Application) work (npm install, etc.)**
-
---------------------------------------------------------------------
---------------------------------------------------------------------
-
-
-## Detailed procedure: Setting eShopOnContainers up in a Visual Studio 2017 development machine
-Visual Studio 2017 with its built-in Docker Tools adds a number of very convenient features which are solid reasons why you'd want to use VS 2017 when developing Docker container based applications. The most important features are:
-* Multi-container debugging, supporting true microservice scenarios
-* Windows Server Containers for .NET Framework apps
-* Addition of CI build definition using a docker-compose.ci.build.yml file at the solution level.
-* Configure Continuous Integration experience for setting up CI/CD with VSTS to Azure Container Services
-
-Being the first one (Multi-container debugging, supporting true microservice scenarios) the most loved feature, probably.
-So, here's how to setup a VS 2017 environment where you can test eShopOnContainers.
-
-### GitHub branch to use
-By default, use the MASTER branch which supports .CSPROJ and VS 2017.
-
-### Software requirements
-Software installation requirements for a Windows dev machine with Visual Studio 2017 and Docker for Windows:
-- 
-
-#### Share drives in Docker settings (In order to deploy and debug with Visual Studio 2017)
-(Note, this is not required if running from Docker CLI with docker-compose up and using VS 2015 or any other IDE or Editor)
-
-
-### IMPORTANT: Open ports in local Firewall so Authentication to the STS (Security Token Service container) can be done through the 10.0.75.1 IP which should be available and already setup by Docker. Also needed for client remote apps like Xamarin app or SPA app in remote browser.
-- You can manually create a rule in your local firewall in your development machine or you can also create that rule by just executing the add-firewall-docker.ps1 script available in the solution's **cli-windows** folder.
-- Basically, you need to open the ports 5100 to 5105 that are used by the solution by creating an IN-BOUND RULE in your firewall, as shown in the screenshot below (for Windows).
-
-
-
-### Installing and configuring Visual Studio 2017 in your development machine
-
-#### Install Visual Studio 2017
-Once you have the bits downloaded locally, run the VS 2017 setup file and select the following workloads depending on the apps you intend to test or work with:
-
-##### Working only with the server side (Microservices and web applications) - Workloads
-
-- ASP.NET and web development
-- .NET Core cross-platofrm development
-- Azure development (Optional) - It is optional but recommended in case you want to deploy to Docker hosts in Azure or use any other infrastructure in Azure.
-
-
-##### Working with the mobile app (Xamarin Mobile apps for iOS, Android and Windows UWP) - Workloads
-If you also want to test/work with the eShopOnContainer model app based on Xamarin, you need to install the following additional workloads:
-- Mobile development with .NET (Xamarin)
-- Universal Windows Platform development
-- .NET desktop development (Optional) - This is not required, but just in case you also want to make tests consuming the microservices from WPF or WinForms desktop apps
-
-
-
-IMPORTANT: As mentioned above, make sure you are NOT installing Google's Android emlulator with Intel HAXM hypervisor or you will run on an incompatibility and Hyper-V won't work in your machine, therefore, Docker for Windows wont work when trying to run the Linux host or any host witih Hyper-V.
-
-Make sur eyou are NOT selecting
-the highlighted options below with a red arrows:
-
-
-
-
-### Clone the eShopOnContainers code from GitHub
-By default, clone the MASTER branch which is VS 2017 comaptible:
-
-
-
-So make sure you switch to that branch in VS 2017 after cloning or clone that beanch with a Git command, from command prompt or PowerShell, similar to:
-
- git clone https://github.com/dotnet/eShopOnContainers.git
-
-
-### Open eShopOnContainers solution, Build, Run
-
-#### Open eShopOnContainers solution in Visual Studio 2017
-
-- If testing/working only with the server-side applications and services, open the solution: **eShopOnContainers-ServicesAndWebApps.sln**
-
-- If testing/working either with the servier-side applications and services plus the Xamarin mobile apps, open the solution: **eShopOnContainers.sln**
-
-Below you can see the full **eShopOnContainers-ServicesAndWebApps.sln** solution (server side) opened in Visual Studio 2017:
-
-
-
-Note how VS 2017 loads the docker-compose.yml files in a special node-tree so it uses that configuration to deploy/debug all the containers configured, at the same time into your Docker host.
-
-#### Build the Web SPA application with NPM
-If you want to run/test the web eShopOnContainers SPA (Single Page Application) client in adition to the regular MVC Web app, you need to install certain dependencies for the client side and build it with "npm build", as the client side of the SPA app is based on ANGULAR 2, TypeScript and other JS frameworks and compilation that needs to happen before building the Docker images.
-The process is described in detail here:
-https://github.com/dotnet/eShopOnContainers/wiki/06.-Setting-the-Web-SPA-application-up
-
-Come back to this point when you finished with the "Setting the SPA up" process.
-
-
-#### Build and run eShopOnContainers from Visual Studio 2017
-
-##### Set docker-compose as the default StartUp project
-In case it is not your "by default project", right click on the "docker-compose" node and select the "Set as Startup Project" menu option, as shwon below:
-
-
-At this point, after waiting sometime for the Nuget packages to be properly restored, you should be able to build the whole solution or even directly deploy/debug it into Docker by simple hitting F5 or pressing the debug "Play" button that now should be labeled as "Docker":
-
-
-
-VS 2017 should compile the .NET projects, then create the Docker images and finally deploy the containers in the Docker host (your by default Linux VM in Docker for Windows).
-Note that the first time you hit F5 it'll take more time, a few minutes at least, because in addition to compile your bits, it needs to pull/download the base images (SQL for Linux Docker Image, Redis Image, ASPNET image, etc.) and register them in the local image repo of your PC. The next time you hit F5 it'll be much faster.
-
-Finally, because the docker-compose configuration project is configured to open the MVC application, it should open your by default browser and show the MVC application with data coming from the microservices/containers:
-
-
-Here's how the docker-compose configuration project is configured to open the MVC application:
-
-
-
-Finally, you can check out how the multiple containers are runnin in your Docker host by running the command **"docker ps"** like below:
-
-
-
-You can see the 8 containers are running and what ports are being exposed, etc.
-
-### Debug with several breakpoints across the multiple containers/projects
-
-Something very compelling and productive in VS 2017 is the capability to debug several breakpoints across the multiple containers/projects.
-For instance, you could set a breakpoint in a controller within the MVC web app plus a second breakpoint in a second controller within the Catalog Web API microservice, then refresh the browser if you were still running the app or F5 again, and VS will be stopping within your microservices running in Docker as shown below! :)
-
-Breakpoint at the MVC app running as Docker container in the Docker host:
-
-
-Press F5 again...
-
-Breakpoint at the Catalog microservice running as Docker container in the Docker host:
-
-
-And that's it! Super simple! Visual Studio is handling all the complexities under the covers and you can directly do F5 and debug a multi-container application!
-
-
-### Test the SPA Web app
-While having the containers running, open a browser and type `http://localhost:5104/` and hit enter.
-You should see the SPA application like in the following screenshot:
-
-
-- - -### Test a microservice's Swagger interface (i.e. the Catalog microservice) -While having the containers running, open a browser and type `http://localhost:5101` and hit enter. -You should see the Swagger page for that microservice that allows you to test the Web API, like in the following screenshot: - -
-
-Then, after providing the size (i.e. 10) and the current page (i.e. 1) for the data of the catalog, you can run the service hitting the "Try it out!" button and see the returned JSON Data:
-
-
-- ----- - -### Testing all the applications and microservices -Once the containers are deployed, you should be able to access any of the services in the following URLs or connection string, from your dev machine: - - -- Web MVC: http://localhost:5100 -- Web Spa: http://localhost:5104 (Important, check how to set up the SPA app and requirements before building the Docker images. Instructions at https://github.com/dotnet/eShopOnContainers/wiki/06.-Setting-the-Web-SPA-application-up) -- Catalog microservice: http://localhost:5101 (Not secured) -- Ordering microservice: http://localhost:5102 (Requires token for authorization) -- Basket microservice: http://localhost:5103 (Requires token for authorization) -- Identity microservice: http://localhost:5105 -- Orders database (SQL Server connection string): Server=tcp:localhost,5432;Database=Microsoft.eShopOnContainers.Services.OrderingDb;User Id=sa;Password=Pass@word; -- Catalog database (SQL Server connection string): Server=tcp:localhost,5434;Database=CatalogDB;User Id=sa;Password=Pass@word -- ASP.NET Identity database (SQL Server connection string): Server=localhost,5433;Database=aspnet-Microsoft.eShopOnContainers;User Id=sa;Password=Pass@word -- Basket data (Redis): listening at localhost:6379 - -#### Creating and Order and Authenticating on the Web MVC application with the DemoUser@microsoft.com user account -When you try the Web MVC application by using the url http://localhost:5100, you'll be able to test the home page which is also the catalog page. But if you want to add articles to the basket you need to login first at the login page which is handled by the STS microservice/container (Security Token Service). At this point, you could register your own user/customer or you can also use a convenient default user/customer named **demoUser@microsoft.com** so you don't need to register your own user and it'll be easier to test. -The credentials for this demo user are: -- User: **demouser@microsoft.com** -- Password: **Pass@word1** - -Below you can see the login page when providing those credentials. -
-
-#### Trying the Xamarin.Forms mobile apps for Android, iOS and Windows
-You can deploy the Xamarin app to real iOS, Android or Windows devices.
-You can also test it on an Android Emulator based on Hyper-V like the Visual Studio Android Emulator (Do NOT install the Google's Android emulator or it will break Docker and Hyper-V, as mentioned aboce).
-
-By default, the Xamarin app shows fake data from mock-services. In order to really access the microservices/containers in Docker from the mobile app, you need to:
- - Disable mock-services in the Xamarin app by setting the UseMockServices = false in the App.xaml.cs and specify the host IP in BaseEndpoint = "http://10.106.144.28" at the GlobalSettings.cs. Both files in the Xamarin.Forms project (PCL).
- - Another alternative is to change that IP through the app UI, by modifying the IP address in the Settings page of the App as shown in the screenshot below.
-- In addition, you need to make sure that the used TCP ports of the services are open in the local firewall. 
-
-
-## Sending feedback and pull requests
-We'd appreciate to your feedback, improvements and ideas.
-You can create new issues at the issues section, do pull requests and/or send emails to eshop_feedback@service.microsoft.com
-
-## Questions
-[QUESTION] Answer +1 if the solution is working for you (Through VS2017 or CLI environment):
-https://github.com/dotnet/eShopOnContainers/issues/107
-
-
diff --git a/03.-Setting-the-eShopOnContainers-solution-up-in-a-Windows-CLI-environment-(dotnet-CLI,-Docker-CLI-and-VS-Code).md b/03.-Setting-the-eShopOnContainers-solution-up-in-a-Windows-CLI-environment-(dotnet-CLI,-Docker-CLI-and-VS-Code).md
deleted file mode 100644
index 5b813ef..0000000
--- a/03.-Setting-the-eShopOnContainers-solution-up-in-a-Windows-CLI-environment-(dotnet-CLI,-Docker-CLI-and-VS-Code).md
+++ /dev/null
@@ -1,271 +0,0 @@
-## Want to try it out from the CLI?
-
-Main steps:
-
-```
-- Git clone https://github.com/dotnet/eShopOnContainers.git
-- Docker-compose -f docker-compose.ci.build.yml up
-- Docker-compose up
-```
-NOTE: In order for the authentication based on the STS (Security Token Service) to properly work and have access from remote client apps like the Xamarin mobile app, you also need to open the ports in your firewall as specified in the procedure below.
-For further instructions, especially if this is the first time you are going to try .NET Core on Docker, see the detailed instructions below. This is also important in order to make the SPA app (Single Page Application) to work as there are some considerations (npm install, etc.) in regards when using NPM from Windows and Linux (the build container).
-
---------------------------------------------------------------------
---------------------------------------------------------------------
-
-## Detailed procedure - Setting eShopOnContainers up in a CLI and Windows based development machine
-This CLI environment means that you want to build/run by using the CLI (Command line interface) available in .NET Core (dotnetcore) and Docker CLI.
-
-
-### Install NPM
-In order to be able to build the JavaScript dependencies from command line by using npm you need to install npm globally.
-
-NPM is bundled with NODE.JS. Installing NPM and NODE is pretty straightforward by using the installer package available at https://nodejs.org/en/
-
-
-You can install the version "Recommended For Most Users" of Node which at the moment of this writing was v6.10.0 LTS.
-
-
-
-
-
-## Clone the eShopOnContainers GitHub code Repository into your dev machine
-
-Clone the code from: https://github.com/dotnet/eShopOnContainers.git
-as in the following screenshot:
-
-
-## Get NPM dependencies for the SPA application
-
-Move to the SPA app folder (`cd eShopOnContainers\src\Web\WebSPA`) and run `npm install`
-
-After a successful execution of npm intall, move to the next step.
-
-
-## Build the bits through the 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.
-
-Move to the root folder of the solution: 
-
-The first time you run this command it'll take some more additional time as it needs to pull/download the aspnet-build image with all the SDKs as part of that build-image, so it'll take its time.
-
-
-At this point you have the .NET bits ready. Now, create the Docker images and run the containers.
-
-### Build Images and Deploy containers into your Docker host
-
-You can build the Docker images and deploy the containers to a regularDocker host by using the Docker CLI tool `docker-compose up` which is very convenient for multi-container applications as it can build all the Docker images for you and then spin-up all the multiple containers of your application, all with a single command.
-If you don't want to deploy the containers but only build the images, you can do so by running `docker-compose build`
-These are the steps:
-
-- **Build images and run your containers in your local host:** Open your favorite command tool (PowerShell od CommandLine in Windows / Bash in Mac) and move to the root directory of the solution where the docker-compose.yml files are located and run the command `docker-compose up`. If this is the first time you run it, it will also build the docker images. Other than that, you could also force to build the images by running `docker-compose build` previously.
-When running `docker-compose up` you should see something similar to the following screenshot in the PowerShell command window, although it will much longer than that, building the images the first time and showing many internal SQL commands from the services when populating sample data for your application.
-
- `docker-compose up`
- 
-
- Note that the first time you try to build any image or run any container (with docker run or docker-compose) it detects that it needs the base images you are using, like the SQL Server image and the Redis image, so it will pull or download those base images from the Internet, from the public repo at the Docker registry named DOCKER HUB, by pulling the "microsoft/mssql-server-linux" which is the base image for the SQL Server for Linux on containers, and the "library/redis" which is the base Redis image. Therefore, the first time you run docker-compose it might take a few minutes pulling those images before it spins up your custom containers.
- The next time you run docker-compose up, since it'll have those base images already pulled/downloaded, it will be much faster.
-
- Because in eShopOnContainers' docker-compose.yml files it is also specified to build the custom Docker images, it is building it, like in the screenshot below (part of the same command execution):
- 
-
- Finally, you can see how the scripts waits after deploying all the containers:
- 
-
-- The next time you run "docker-compose up" again (you don't need to repeat it now), because now you already have all the base images downloaded and registered in your local repo and your custom images built and ready to go, it'll be much faster since it just needs to deploy the containers, like the following screenshot:
-
-
-- Check out the containers running in your Docker host: Once docker-compose up finishes, you will have the original PowerShell window busy and showing the execution's output in a "wait state", so in order to ask to Docker about "how it went" and see what containers are running, you need to open a second PowerShell window and type "docker ps" so you'll see all the running containers, as shown in the following screenshot.
-
-
- You can see the 6 custom containers running the 4 microservices plus the 2 web applications. In addition you have the SQL container with the databases (if you had a lot of memory, you could put one database per SQL container, too) and the Redis cache for the basket microservice data.
-
-- You can also check out with Docker CLI the images generated by typing in the PowerShell console the command: `docker images`
-
-
- Those Docker images are the ones you have available in your local image repository in your machine.
-You might have additional images, but at least, you should see the following list of images which are 6 custom images starting with the prefix "eshop" which is the name of the image repo. The rest of the images that are not starting with "eshop" will probably be official base-images like the microsoft/aspnetcore or the SQL Server for Linux images.
-
-### Test the MVC Web app
-Open a browser and type `http://localhost:5100/` and hit enter.
-You should see the MVC application like in the following screenshot:
-
-
-
-
-`Editing a .yml file`
-
-
-It is also recommended to install the C# extension and the Docker extension for VS Code:
-
-
-
-----
-
-### Testing all the applications and microservices
-Once the containers are deployed, you should be able to access any of the services in the following URLs or connection string, from your dev machine:
-
-
-
-
-## Build, Ship, Run
-In the global directory you will find the scripts needed to build, deploy and run the application into your local Docker development machine. The steps are the following:
-
-### Compile the .NET apps and Build the Docker images
-- Open a PowerShell window in Windows, move to the root folder of your solution and run the build-images.ps1 script file like in the following screenshot.
-
-IMPORTANT: This script deletes all the Docker images registered in your local dev machine repository before creating the new images, so it is starting from a 100% clean state. If you don't want your local images in your PC to be deleted, edit and change the build-images.ps1 script file before you run it.
-
-- This Power-Shell script that you will find in the root directory of the solution is responsible for building the .NET applications, copy the binaries in a pub folder and use Docker CLI commands to build the custom Docker images needed to run the containers. You can see how to run that PowerShell script in the screenshot below:
-
-
-- Once it finishes, you can check it out with Docker CLI if the images were generated correctly by typing in the PowerShell console the command: `docker images`
-
-Those Docker images are the ones you have available in your local image repository in your machine.
-You might have additional images, but at least, you should see the following list of images which are 6 custom images starting with the prefix "eshop" which is the name of the image repo. The rest of the images that are not starting with "eshop" will probably be official base-images like the microsoft/aspnetcore or the SQL Server for Linux images.
-
-### Deploy containers into your Docker host
-You can deploy Docker containers to a regularDocker host either by using the `docker run` command which need to be executed once per microservice, or by using the CLI tool `docker-compose up` which is very convenient for multi-container applications as it can spin-up all the multiple containers in your application with a single command. These are the steps:
-- Run your containers in your local host: Open your favorite command tool (PowerShell od CommandLine in Windows / Bash in Mac) and move to the root directory of the solution where the docker-compose.yml file is located and run the command `docker-compose up`. When running "docker-compose up" you should see something similar to the following screenshot in the PowerShell command window, although it will much longer than that, also showing many internal SQL commands from the services when populating the first time the sample data.
-`docker-compose up`
-
-
-- Note that the first time you run any container (with docker run or docker-compose) it detects that it needs the base images we are using, like the SQL Server image and the Redis image, so it will pull or download those base images from the Internet, from the public repo at the Docker registry named DOCKER HUB, by pulling the "microsoft/mssql-server-linux" which is the base image for the SQL Server for Linux on containers, and the "library/redis" which is the base Redis image. Therefore, the first time you run docker-compose it might take a few minutes pulling those images before it spins up your custom containers.
-The next time you run docker-compose up, since it'll have those base images already pulled/downloaded, it will just start the containers, like in the following screenshot:
-
-
-- Check out the containers running in your Docker host: Once docker-compose up finishes after a few minutes, you will have that PowerShell showing the execution's output in a "wait state", so in order to ask to Docker about "how it went" and see what containers are running, you need to open a second PowerShell window and type "docker ps" so you'll see all the running containers, as shown in the following screenshot.
-
-You can see the 6 custom containers running the microservices plus the 2 web applications. In adition you have the containers with the SQL databases and the Redis cache for the basket microservice data.
-
-
-#### IMPORTANT: Open ports in Firewall so Authentication to the STS (Security Token Service container) can be done through the 10.0.75.1 IP which should be available and already setup by Docker
-- You can manually create a rule in your local firewall in your development machine or you can also create that rule by just executing the add-firewall-docker.ps1 script in the solution's root.
-- Basically, you need to open the ports 5100 to 5105 that are used by the solution by creating an IN-BOUND RULE in your firewall, as shown in the screenshot below (for Windows).
-
-If you don't do this step you might have issues because of using different versions from VS versus the command line accessing the same JavaScript code from both environments.
-See:
-http://www.hanselman.com/blog/VisualStudio2015FixingDependenciesNpmNotInstalledFromFseventsWithNodeOnWindows.aspx
-
-
-### Build the SPA app with NPM
-Now, you need to build the SPA app (TypeScript and Angular 2 based client app) with NPM.
-* Open a command-prompt window and move to the root of the SPA application (src\Web\WebSPA\eShopOnContainers.WebSPA)
-* Run the command npm install as shown below:
-
-* Then, run the command npm run build:prod as shown below:
-
-
- If you get an error like "Node Sass could not find a binding for your current environment: Windows 64-bit with Node.js 6.x", then run the command npm rebuild node-sass as in the following screenshot:
- 
- Then, run again the npm run build:prod command that should finish with no errors.
-
- 
-
-#### (Optional) Run NPM tasks from within Visual Studio 2017
-
-As the chosen workload method when developing a client frontend app (JS frameworks, etc.), the developer has to be able to trigger the npm tasks when he wants.
-Of course, he can always open a command propmt and run npm from the CLI as you just did in the steps above (which is most front-end devs do, in fact).
-However, you can also run npm tasks inside Visual Studio if you install the following VS extension: https://marketplace.visualstudio.com/items?itemName=MadsKristensen.NPMTaskRunner
-
-This extension adds to the "Task Runner Explorer" the capabailities to run npm tasks (since, out of the box, only gulp/grunt tasks are supported by VS2017). After this extension is installed you can run npm tasks from inside VS2017 and also set build bindings if you wanted.
-
-
-
-This extension honors the VS External Web Tools configuration, and allows you to use bindings, so if you want to run npm tasks automatically on every VS build, you could do so. This is not set as default in the eShopOnContainers provided code as it would slow down each VS build with the npm build tasks.
-
-### Build the Docker images and Deploy the containers
-At this point, if you were originally following the eShopOnContainer setup for any environment and came to this page just to setup the SPA app, now go back to your original setup instructions page. Other than that, you can in any case choose between any of the following options to build and deploy the Docker containers:
-
-1. **VS 2017 based:** Build and deploy in a single step from Visual Studio 2017 as explained in this page: https://github.com/dotnet/eShopOnContainers/wiki/02.-Setting-eShopOnContainer-solution-up-in-a-Visual-Studio-2017-environment
-
-2. **CLI on Windows:** Build the .NET bits with the build-container based on dontnet CLI and Docker CLI, as explained in this page: https://github.com/dotnet/eShopOnContainers/wiki/03.-Setting-the-eShopOnContainers-solution-up-in-a-Windows-CLI-environment-(dotnet-CLI,-Docker-CLI-and-VS-Code)
-
-3. **CLI on Mac:** Build the .NET bits with the build-container based on dontnet CLI and Docker CLI, as explained in this page: https://github.com/dotnet/eShopOnContainers/wiki/04.-Setting-eShopOnContainer-solution-up-in-a-Mac,-VS-Code-and-CLI-environment--(dotnet-CLI,-Docker-CLI-and-VS-Code)
-
-
-## Sending feedback and pull requests
-We'd appreciate to your feedback, improvements and ideas.
-You can create new issues at the issues section, do pull requests and/or send emails to eshop_feedback@service.microsoft.com
\ No newline at end of file
diff --git a/07.-Setting-up-the-Xamarin-mobile-apps.md b/07.-Setting-up-the-Xamarin-mobile-apps.md
deleted file mode 100644
index ae7be7e..0000000
--- a/07.-Setting-up-the-Xamarin-mobile-apps.md
+++ /dev/null
@@ -1,6 +0,0 @@
-To be implemented soon.
-
-
-## Sending feedback and pull requests
-We'd appreciate to your feedback, improvements and ideas.
-You can create new issues at the issues section, do pull requests and/or send emails to eshop_feedback@service.microsoft.com
\ No newline at end of file
diff --git "a/08.-Deploying-\"Production-Staging\"-config-for-remote-browsers-or-Xamarin-mobile-apps-(Using-external-DNS-name-or--external-IP-instead-of-LOCALHOST).md" "b/08.-Deploying-\"Production-Staging\"-config-for-remote-browsers-or-Xamarin-mobile-apps-(Using-external-DNS-name-or--external-IP-instead-of-LOCALHOST).md"
deleted file mode 100644
index 8d45b4d..0000000
--- "a/08.-Deploying-\"Production-Staging\"-config-for-remote-browsers-or-Xamarin-mobile-apps-(Using-external-DNS-name-or--external-IP-instead-of-LOCALHOST).md"
+++ /dev/null
@@ -1,12 +0,0 @@
-DRAFT - TBD in further details.
-Basically, the docker-compose needs to be using the "production/staging" config, with:
-
-**docker-compose -f docker-compose.yml -f docker-compose.prod.yml up -d**
-
-This is using the [docker-compose.prod.yml](https://github.com/dotnet/eShopOnContainers/blob/master/docker-compose.prod.yml) which is providing an specific external DNS or IP configured by default at the [.env file](https://github.com/dotnet/eShopOnContainers/blob/master/.env) as:
-
-ESHOP_EXTERNAL_DNS_NAME_OR_IP=192.168.88.248
-
-You could override with values from environment variables from your runtime/shell, as well.
-
-
diff --git a/Home.md b/Home.md
deleted file mode 100644
index 762bb80..0000000
--- a/Home.md
+++ /dev/null
@@ -1,32 +0,0 @@
-# Welcome to the eShopOnContainers wiki!
-
-## Questions
-[QUESTION] Answer +1 if the solution is working for you (Through VS2017 or CLI environment):
-https://github.com/dotnet/eShopOnContainers/issues/107
-
-## Roadmap
-https://github.com/dotnet/eShopOnContainers/wiki/01.-Roadmap-and-Milestones-for-future-releases
-
-## Setting up your development environment for eShopOnContainers
-### Visual Studio 2017 and Windows based
-This is the more straightforward way to get started:
-https://github.com/dotnet/eShopOnContainers/wiki/02.-Setting-eShopOnContainer-solution-up-in-a-Visual-Studio-2017-environment
-
-### CLI and Windows based
-For those who prefer the CLI on Windows, using dotnet CLI, docker CLI and VS Code for Windows:
-https://github.com/dotnet/eShopOnContainers/wiki/03.-Setting-the-eShopOnContainers-solution-up-in-a-Windows-CLI-environment-(dotnet-CLI,-Docker-CLI-and-VS-Code)
-
-### CLI and Mac based
-For those who prefer the CLI on a Mac, using dotnet CLI, docker CLI and VS Code for Mac:
-https://github.com/dotnet/eShopOnContainers/wiki/04.-Setting-eShopOnContainer-solution-up-in-a-Mac,-VS-Code-and-CLI-environment--(dotnet-CLI,-Docker-CLI-and-VS-Code)
-
-## Related Documentation
-### Guide/eBook: Architecting and Developing Containerized and Microservice based .NET Applications
-https://github.com/dotnet/eShopOnContainers/blob/master/docs/architecting-and-developing-containerized-and-microservice-based-net-applications-ebook-early-draft.pdf
-
-##Issues:
-https://github.com/dotnet/eShopOnContainers/issues
-
-## Sending feedback and pull requests
-We'd appreciate to your feedback, improvements and ideas.
-You can create new issues at the issues section, do pull requests and/or send emails to eshop_feedback@service.microsoft.com
\ No newline at end of file
diff --git a/img/Bower_and_Gulp_setup.png b/img/Bower_and_Gulp_setup.png
deleted file mode 100644
index 78470a4..0000000
Binary files a/img/Bower_and_Gulp_setup.png and /dev/null differ
diff --git a/img/Generating_Docker_Images.png b/img/Generating_Docker_Images.png
deleted file mode 100644
index a255415..0000000
Binary files a/img/Generating_Docker_Images.png and /dev/null differ
diff --git a/img/Multiple-Distributed-Dependencies.png b/img/Multiple-Distributed-Dependencies.png
deleted file mode 100644
index c06f7b5..0000000
Binary files a/img/Multiple-Distributed-Dependencies.png and /dev/null differ
diff --git a/img/Node_setup_for_npm.png b/img/Node_setup_for_npm.png
deleted file mode 100644
index 6332950..0000000
Binary files a/img/Node_setup_for_npm.png and /dev/null differ
diff --git a/img/cli-windows/build-bits-1.png b/img/cli-windows/build-bits-1.png
deleted file mode 100644
index 28689c5..0000000
Binary files a/img/cli-windows/build-bits-1.png and /dev/null differ
diff --git a/img/cli-windows/build-bits-2.png b/img/cli-windows/build-bits-2.png
deleted file mode 100644
index d1261d7..0000000
Binary files a/img/cli-windows/build-bits-2.png and /dev/null differ
diff --git a/img/cli-windows/build-bits-3-catalog-bits.png b/img/cli-windows/build-bits-3-catalog-bits.png
deleted file mode 100644
index e637696..0000000
Binary files a/img/cli-windows/build-bits-3-catalog-bits.png and /dev/null differ
diff --git a/img/cli-windows/cd-to-root-folder.png b/img/cli-windows/cd-to-root-folder.png
deleted file mode 100644
index 97b0926..0000000
Binary files a/img/cli-windows/cd-to-root-folder.png and /dev/null differ
diff --git a/img/cli-windows/docker-compose-ci-compose-file-ending.png b/img/cli-windows/docker-compose-ci-compose-file-ending.png
deleted file mode 100644
index 1ed7791..0000000
Binary files a/img/cli-windows/docker-compose-ci-compose-file-ending.png and /dev/null differ
diff --git a/img/cli-windows/docker-compose-ci-compose-file.png b/img/cli-windows/docker-compose-ci-compose-file.png
deleted file mode 100644
index 9ef7337..0000000
Binary files a/img/cli-windows/docker-compose-ci-compose-file.png and /dev/null differ
diff --git a/img/cli-windows/docker-compose-pulling-aspnetbuild-image.png b/img/cli-windows/docker-compose-pulling-aspnetbuild-image.png
deleted file mode 100644
index 5d939d0..0000000
Binary files a/img/cli-windows/docker-compose-pulling-aspnetbuild-image.png and /dev/null differ
diff --git a/img/cli-windows/docker-compose-up-0-initial-pull-images.png b/img/cli-windows/docker-compose-up-0-initial-pull-images.png
deleted file mode 100644
index 56b6fc9..0000000
Binary files a/img/cli-windows/docker-compose-up-0-initial-pull-images.png and /dev/null differ
diff --git a/img/cli-windows/docker-compose-up-1.1.png b/img/cli-windows/docker-compose-up-1.1.png
deleted file mode 100644
index 0a2b7bc..0000000
Binary files a/img/cli-windows/docker-compose-up-1.1.png and /dev/null differ
diff --git a/img/cli-windows/docker-compose-up-1.2.png b/img/cli-windows/docker-compose-up-1.2.png
deleted file mode 100644
index 08bfa51..0000000
Binary files a/img/cli-windows/docker-compose-up-1.2.png and /dev/null differ
diff --git a/img/cli-windows/docker-compose-up-1.png b/img/cli-windows/docker-compose-up-1.png
deleted file mode 100644
index 649719c..0000000
Binary files a/img/cli-windows/docker-compose-up-1.png and /dev/null differ
diff --git a/img/cli-windows/docker-compose-up-2.png b/img/cli-windows/docker-compose-up-2.png
deleted file mode 100644
index fb086d2..0000000
Binary files a/img/cli-windows/docker-compose-up-2.png and /dev/null differ
diff --git a/img/cli-windows/docker-compose-up-ending-wait.png b/img/cli-windows/docker-compose-up-ending-wait.png
deleted file mode 100644
index 6742e7b..0000000
Binary files a/img/cli-windows/docker-compose-up-ending-wait.png and /dev/null differ
diff --git a/img/cli-windows/docker-ps-with-all-microservices.png b/img/cli-windows/docker-ps-with-all-microservices.png
deleted file mode 100644
index ad9757a..0000000
Binary files a/img/cli-windows/docker-ps-with-all-microservices.png and /dev/null differ
diff --git a/img/cli-windows/git-clone-powershell.png b/img/cli-windows/git-clone-powershell.png
deleted file mode 100644
index fa63d9b..0000000
Binary files a/img/cli-windows/git-clone-powershell.png and /dev/null differ
diff --git a/img/cli-windows/list-of-images.png b/img/cli-windows/list-of-images.png
deleted file mode 100644
index 1937f1b..0000000
Binary files a/img/cli-windows/list-of-images.png and /dev/null differ
diff --git a/img/cli-windows/powershell-set-execution-policy.png b/img/cli-windows/powershell-set-execution-policy.png
deleted file mode 100644
index b1aa25b..0000000
Binary files a/img/cli-windows/powershell-set-execution-policy.png and /dev/null differ
diff --git a/img/cli-windows/vs-code-1.png b/img/cli-windows/vs-code-1.png
deleted file mode 100644
index 62f661f..0000000
Binary files a/img/cli-windows/vs-code-1.png and /dev/null differ
diff --git a/img/cli-windows/vs-code-2.png b/img/cli-windows/vs-code-2.png
deleted file mode 100644
index ff93b7e..0000000
Binary files a/img/cli-windows/vs-code-2.png and /dev/null differ
diff --git a/img/cli-windows/vs-code-3-extensions.png b/img/cli-windows/vs-code-3-extensions.png
deleted file mode 100644
index e5d6773..0000000
Binary files a/img/cli-windows/vs-code-3-extensions.png and /dev/null differ
diff --git a/img/docker-compose-up-1.png b/img/docker-compose-up-1.png
deleted file mode 100644
index 6aa3b1c..0000000
Binary files a/img/docker-compose-up-1.png and /dev/null differ
diff --git a/img/docker-compose-up-2.png b/img/docker-compose-up-2.png
deleted file mode 100644
index 705d839..0000000
Binary files a/img/docker-compose-up-2.png and /dev/null differ
diff --git a/img/docker-ps-with-all-microservices.png b/img/docker-ps-with-all-microservices.png
deleted file mode 100644
index b803ab3..0000000
Binary files a/img/docker-ps-with-all-microservices.png and /dev/null differ
diff --git a/img/docker_settings.png b/img/docker_settings.png
deleted file mode 100644
index b2641c7..0000000
Binary files a/img/docker_settings.png and /dev/null differ
diff --git a/img/docker_settings_shared_drives.png b/img/docker_settings_shared_drives.png
deleted file mode 100644
index 1027a43..0000000
Binary files a/img/docker_settings_shared_drives.png and /dev/null differ
diff --git a/img/eShopOnContainers_Architecture_Diagram.png b/img/eShopOnContainers_Architecture_Diagram.png
deleted file mode 100644
index 5a45657..0000000
Binary files a/img/eShopOnContainers_Architecture_Diagram.png and /dev/null differ
diff --git a/img/ebook_arch_dev_microservices_containers_cover.png b/img/ebook_arch_dev_microservices_containers_cover.png
deleted file mode 100644
index 2a959ac..0000000
Binary files a/img/ebook_arch_dev_microservices_containers_cover.png and /dev/null differ
diff --git a/img/ebook_containers_lifecycle.png b/img/ebook_containers_lifecycle.png
deleted file mode 100644
index 650703a..0000000
Binary files a/img/ebook_containers_lifecycle.png and /dev/null differ
diff --git a/img/eshop-webmvc-app-screenshot.png b/img/eshop-webmvc-app-screenshot.png
deleted file mode 100644
index 0c02fe8..0000000
Binary files a/img/eshop-webmvc-app-screenshot.png and /dev/null differ
diff --git a/img/eshop-webspa-app-screenshot.png b/img/eshop-webspa-app-screenshot.png
deleted file mode 100644
index 854c5e8..0000000
Binary files a/img/eshop-webspa-app-screenshot.png and /dev/null differ
diff --git a/img/eshop_cover.png b/img/eshop_cover.png
deleted file mode 100644
index 5e2f01b..0000000
Binary files a/img/eshop_cover.png and /dev/null differ
diff --git a/img/eshop_logo.png b/img/eshop_logo.png
deleted file mode 100644
index ecbcd25..0000000
Binary files a/img/eshop_logo.png and /dev/null differ
diff --git a/img/firewall-rule-for-eshop.png b/img/firewall-rule-for-eshop.png
deleted file mode 100644
index 996b632..0000000
Binary files a/img/firewall-rule-for-eshop.png and /dev/null differ
diff --git a/img/list-of-images.png b/img/list-of-images.png
deleted file mode 100644
index 3985db2..0000000
Binary files a/img/list-of-images.png and /dev/null differ
diff --git a/img/login-demo-user.png b/img/login-demo-user.png
deleted file mode 100644
index d5d9cf6..0000000
Binary files a/img/login-demo-user.png and /dev/null differ
diff --git a/img/netcore-sdk-11-installer.png b/img/netcore-sdk-11-installer.png
deleted file mode 100644
index 559c6a4..0000000
Binary files a/img/netcore-sdk-11-installer.png and /dev/null differ
diff --git a/img/spa/installing_npm_node.png b/img/spa/installing_npm_node.png
deleted file mode 100644
index b800022..0000000
Binary files a/img/spa/installing_npm_node.png and /dev/null differ
diff --git a/img/spa/npm-install.png b/img/spa/npm-install.png
deleted file mode 100644
index 113713a..0000000
Binary files a/img/spa/npm-install.png and /dev/null differ
diff --git a/img/spa/npm-install_full.png b/img/spa/npm-install_full.png
deleted file mode 100644
index 2a3f92d..0000000
Binary files a/img/spa/npm-install_full.png and /dev/null differ
diff --git a/img/spa/npm-rebuild-node-sass.png b/img/spa/npm-rebuild-node-sass.png
deleted file mode 100644
index 309ba51..0000000
Binary files a/img/spa/npm-rebuild-node-sass.png and /dev/null differ
diff --git a/img/spa/npm-run-build-prod-no-errors.png b/img/spa/npm-run-build-prod-no-errors.png
deleted file mode 100644
index 31cc9ee..0000000
Binary files a/img/spa/npm-run-build-prod-no-errors.png and /dev/null differ
diff --git a/img/spa/npm-run-build-prod.png b/img/spa/npm-run-build-prod.png
deleted file mode 100644
index 3aede95..0000000
Binary files a/img/spa/npm-run-build-prod.png and /dev/null differ
diff --git a/img/spa/npm-run-build.png b/img/spa/npm-run-build.png
deleted file mode 100644
index 839ad8d..0000000
Binary files a/img/spa/npm-run-build.png and /dev/null differ
diff --git a/img/spa/npm-versions-powershell.png b/img/spa/npm-versions-powershell.png
deleted file mode 100644
index baf7410..0000000
Binary files a/img/spa/npm-versions-powershell.png and /dev/null differ
diff --git a/img/spa/task-runner-with-npm-extension.png b/img/spa/task-runner-with-npm-extension.png
deleted file mode 100644
index d04a6ea..0000000
Binary files a/img/spa/task-runner-with-npm-extension.png and /dev/null differ
diff --git a/img/spa/vs-tools-path-custom-node.png b/img/spa/vs-tools-path-custom-node.png
deleted file mode 100644
index dbe9708..0000000
Binary files a/img/spa/vs-tools-path-custom-node.png and /dev/null differ
diff --git a/img/spa/vs-tools-path-original.png b/img/spa/vs-tools-path-original.png
deleted file mode 100644
index 66fde95..0000000
Binary files a/img/spa/vs-tools-path-original.png and /dev/null differ
diff --git a/img/swagger-catalog-1.png b/img/swagger-catalog-1.png
deleted file mode 100644
index 03538dc..0000000
Binary files a/img/swagger-catalog-1.png and /dev/null differ
diff --git a/img/swagger-catalog-2.png b/img/swagger-catalog-2.png
deleted file mode 100644
index ff30a37..0000000
Binary files a/img/swagger-catalog-2.png and /dev/null differ
diff --git a/img/vs-solution-structure.png b/img/vs-solution-structure.png
deleted file mode 100644
index 76b4edd..0000000
Binary files a/img/vs-solution-structure.png and /dev/null differ
diff --git a/img/vs2017/debug-F5-button.png b/img/vs2017/debug-F5-button.png
deleted file mode 100644
index f6593e7..0000000
Binary files a/img/vs2017/debug-F5-button.png and /dev/null differ
diff --git a/img/vs2017/debugging-mvc-app.png b/img/vs2017/debugging-mvc-app.png
deleted file mode 100644
index e8bd2de..0000000
Binary files a/img/vs2017/debugging-mvc-app.png and /dev/null differ
diff --git a/img/vs2017/debugging-webapi-microservice.png b/img/vs2017/debugging-webapi-microservice.png
deleted file mode 100644
index 95c7ab2..0000000
Binary files a/img/vs2017/debugging-webapi-microservice.png and /dev/null differ
diff --git a/img/vs2017/docker-compose-properties.png b/img/vs2017/docker-compose-properties.png
deleted file mode 100644
index fa1291f..0000000
Binary files a/img/vs2017/docker-compose-properties.png and /dev/null differ
diff --git a/img/vs2017/docker-ps.png b/img/vs2017/docker-ps.png
deleted file mode 100644
index 859c3e9..0000000
Binary files a/img/vs2017/docker-ps.png and /dev/null differ
diff --git a/img/vs2017/github-clone-branch.png b/img/vs2017/github-clone-branch.png
deleted file mode 100644
index 100f20a..0000000
Binary files a/img/vs2017/github-clone-branch.png and /dev/null differ
diff --git a/img/vs2017/set-docker-node-as-default.png b/img/vs2017/set-docker-node-as-default.png
deleted file mode 100644
index b009d34..0000000
Binary files a/img/vs2017/set-docker-node-as-default.png and /dev/null differ
diff --git a/img/vs2017/vs-2017-eshoponcontainers-servicesandwebapps-solution.png b/img/vs2017/vs-2017-eshoponcontainers-servicesandwebapps-solution.png
deleted file mode 100644
index 653c082..0000000
Binary files a/img/vs2017/vs-2017-eshoponcontainers-servicesandwebapps-solution.png and /dev/null differ
diff --git a/img/vs2017/vs2017-f5-with-eshoponcontainers-web-mvc-in-browser.png b/img/vs2017/vs2017-f5-with-eshoponcontainers-web-mvc-in-browser.png
deleted file mode 100644
index 9d8de28..0000000
Binary files a/img/vs2017/vs2017-f5-with-eshoponcontainers-web-mvc-in-browser.png and /dev/null differ
diff --git a/img/vs2017/vs2017_additional_mobile_workloads.png b/img/vs2017/vs2017_additional_mobile_workloads.png
deleted file mode 100644
index 077ffa4..0000000
Binary files a/img/vs2017/vs2017_additional_mobile_workloads.png and /dev/null differ
diff --git a/img/vs2017/vs2017_server_workload.png b/img/vs2017/vs2017_server_workload.png
deleted file mode 100644
index 5e2bb4e..0000000
Binary files a/img/vs2017/vs2017_server_workload.png and /dev/null differ
diff --git a/img/vs2017/xamarin-workload-options.png b/img/vs2017/xamarin-workload-options.png
deleted file mode 100644
index 31a8dea..0000000
Binary files a/img/vs2017/xamarin-workload-options.png and /dev/null differ
diff --git a/img/xamarin-mobile-App.png b/img/xamarin-mobile-App.png
deleted file mode 100644
index 7b63a48..0000000
Binary files a/img/xamarin-mobile-App.png and /dev/null differ
diff --git a/img/xamarin-settings.png b/img/xamarin-settings.png
deleted file mode 100644
index 4379091..0000000
Binary files a/img/xamarin-settings.png and /dev/null differ
diff --git a/img/xamarin/fix-hyperv-for-issue-xamarin-app-minimize-in-vs-android-emulator.png b/img/xamarin/fix-hyperv-for-issue-xamarin-app-minimize-in-vs-android-emulator.png
deleted file mode 100644
index a4d0a3f..0000000
Binary files a/img/xamarin/fix-hyperv-for-issue-xamarin-app-minimize-in-vs-android-emulator.png and /dev/null differ