Skip to content

Commit ba29a1b

Browse files
author
Jim Bennett
authored
Adding powershell instructions (#262)
1 parent 846e357 commit ba29a1b

File tree

3 files changed

+39
-12
lines changed

3 files changed

+39
-12
lines changed

1-getting-started/lessons/1-introduction-to-iot/virtual-device.md

+13-4
Original file line numberDiff line numberDiff line change
@@ -55,18 +55,27 @@ Configure a Python virtual environment and install the pip packages for CounterF
5555

5656
1. Activate the virtual environment:
5757

58-
* On Windows run:
58+
* On Windows:
59+
* If you are using the Command Prompt, or the Command Prompt through Windows Terminal, run:
5960

60-
```cmd
61-
.venv\Scripts\activate.bat
62-
```
61+
```cmd
62+
.venv\Scripts\activate.bat
63+
```
64+
65+
* If you are using PowerShell, run:
66+
67+
```powershell
68+
.\.venv\Scripts\Activate.ps1
69+
```
6370

6471
* On macOS or Linux, run:
6572

6673
```cmd
6774
source ./.venv/bin/activate
6875
```
6976

77+
> 💁 These commands should be run from the same location you ran the command to create the virtual environment. You will never need to navigate into the `.venv` folder, you should always run the activate command and any commands to install packages or run code from the folder you were in when you created the virtual environment.
78+
7079
1. Once the virtual environment has been activated, the default `python` command will run the version of Python that was used to create the virtual environment. Run the following to get the version:
7180

7281
```sh

1-getting-started/lessons/4-connect-internet/README.md

+13-4
Original file line numberDiff line numberDiff line change
@@ -178,18 +178,27 @@ Configure a Python virtual environment and install the MQTT pip packages.
178178

179179
1. Activate the virtual environment:
180180

181-
* On Windows run:
181+
* On Windows:
182+
* If you are using the Command Prompt, or the Command Prompt through Windows Terminal, run:
182183

183-
```cmd
184-
.venv\Scripts\activate.bat
185-
```
184+
```cmd
185+
.venv\Scripts\activate.bat
186+
```
187+
188+
* If you are using PowerShell, run:
189+
190+
```powershell
191+
.\.venv\Scripts\Activate.ps1
192+
```
186193

187194
* On macOS or Linux, run:
188195

189196
```cmd
190197
source ./.venv/bin/activate
191198
```
192199

200+
> 💁 These commands should be run from the same location you ran the command to create the virtual environment. You will never need to navigate into the `.venv` folder, you should always run the activate command and any commands to install packages or run code from the folder you were in when you created the virtual environment.
201+
193202
1. Once the virtual environment has been activated, the default `python` command will run the version of Python that was used to create the virtual environment. Run the following to get the version:
194203

195204
```sh

2-farm/lessons/5-migrate-application-to-the-cloud/README.md

+13-4
Original file line numberDiff line numberDiff line change
@@ -131,18 +131,27 @@ The Azure Functions CLI can be used to create a new Functions app.
131131

132132
1. Activate the virtual environment:
133133

134-
* On Windows run:
134+
* On Windows:
135+
* If you are using the Command Prompt, or the Command Prompt through Windows Terminal, run:
135136

136-
```cmd
137-
.venv\Scripts\activate.bat
138-
```
137+
```cmd
138+
.venv\Scripts\activate.bat
139+
```
140+
141+
* If you are using PowerShell, run:
142+
143+
```powershell
144+
.\.venv\Scripts\Activate.ps1
145+
```
139146

140147
* On macOS or Linux, run:
141148

142149
```cmd
143150
source ./.venv/bin/activate
144151
```
145152

153+
> 💁 These commands should be run from the same location you ran the command to create the virtual environment. You will never need to navigate into the `.venv` folder, you should always run the activate command and any commands to install packages or run code from the folder you were in when you created the virtual environment.
154+
146155
1. Run the following command to create a Functions app in this folder:
147156

148157
```sh

0 commit comments

Comments
 (0)