You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: ReadMe.md
+8Lines changed: 8 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -40,10 +40,18 @@ We have a few modules which are required for building. They're listed in `Requir
40
40
41
41
#### 3. Run the `build.ps1` script.
42
42
43
+
By default, the build script uses [gitversion](/gittols/gitversion) to calculate the version of the build automatically:
44
+
43
45
```powershell
44
46
.\build.ps1
45
47
```
46
48
49
+
If you don't have gitversion handy, you can just specify a version for the `-Semver` parameter:
50
+
51
+
```powershell
52
+
.\build.ps1 -Semver 2.0.0-beta
53
+
```
54
+
47
55
#### 4. Make the compiled module available to Powershell
48
56
49
57
The `.\build.ps1` process will output the path to the folder named with the current version number, like "1.0.0" -- the compiled psm1 and psd1 files are in that folder. In order for PowerShell to find them when you ask it to import, they need to be in the PSModulePath. PowerShell expects to find modules in a folder with a matching name that sits in one of the folders in your PSModulePath.
0 commit comments