ayan.poddar/eShopOnContainers
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

CLI Windows updated

Cesar De la Torre 2017-02-20 19:59:49 -08:00
parent b5c23a48f7
commit 67954520a3
2 changed files with 5 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

BIN
.vs/slnx.sqlite

Binary file not shown.

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

@ -49,12 +49,14 @@ The drive you'll need to share depends on where you place your source code.
<img src="img/firewall-rule-for-eshop.png"> <img src="img/firewall-rule-for-eshop.png">
### .NET Core SDK setup ### .NET Core SDK setup
You need the .NET Core SDK so you can run the .NET Core CLI with commands like "dotnet build", "dotnet publish", etc.
Install the .NET Core SDK from here Install the .NET Core SDK from here
https://www.microsoft.com/net/download/core#/current https://www.microsoft.com/net/download/core#/current
(Current/x64 .NET Core 1.1 SDK Installer, usually) (Current/x64 .NET Core 1.1 SDK Installer, usually)
Run the setup like in the following screenshot: Run the setup like in the following screenshot:
<img src="img/netcore-sdk-installer.png"> <img src="img/netcore-sdk-11-installer.png">
### Node, Bower and Gulp installation ### Node, Bower and Gulp installation
(These steps about installing bower and gulp might not be needed anymore as these are being triggered from the .csproj file in the MVC project at the "PrepublishScript" section). <p> (These steps about installing bower and gulp might not be needed anymore as these are being triggered from the .csproj file in the MVC project at the "PrepublishScript" section). <p>
@ -87,7 +89,7 @@ https://github.com/dotnet/eShopOnContainers/wiki/06.-Setting-the-Web-SPA-applica
These steps are easily performed by running a convenient script already created for you. As mentioned, it is internally using the .NET Core CLI (dotnet). These steps are easily performed by running a convenient script already created for you. As mentioned, it is internally using the .NET Core CLI (dotnet).
- Open a PowerShell window in Windows. Make sure that you have permission to run scripts by running the following command: - Open a PowerShell window in Windows. Make sure that you have permission to run scripts by running the following command:
- **Set-ExecutionPolicy Unrestricted -Scope LocalMachine** `Set-ExecutionPolicy Unrestricted -Scope LocalMachine`
<img src="img/cli-windows/powershell-set-execution-policy.png"> <img src="img/cli-windows/powershell-set-execution-policy.png">
- There is a Power-Shell script that you will find in the <u>root directory of the solution</u> named <b>build-bits.ps1</b> which is responsible for building the .NET applications and copy the binaries into multiple publish folder. - There is a Power-Shell script that you will find in the <u>root directory of the solution</u> named <b>build-bits.ps1</b> which is responsible for building the .NET applications and copy the binaries into multiple publish folder.