Skip to content

Commit 58371ab

Browse files
author
Sean Wheeler
authored
Merging latest into Live (#1925)
* Update the example of `Where-Object -IsNot` (#1841) * Update Example 5 in Group-Object.md (#1845) * removing @{Text=} tags * fixing UTF8 characters * removed empty H3 * added H3 for input and output types * removed mangled UTF8 character * updating Out-* commands with -NoNewLine per Issue 1739 * Fix the example of `Format-Table -DisplayError` (#1848) The example is a `-DisplayError` parameter example. But it uses `-ShowError` parameter. * Fix the example of `Format-Wide -DisplayError` (#1850) * Fix the example of `Format-Custom -DisplayError` (#1849) The example is a -DisplayError parameter example. But it uses -ShowError parameter. * updating set-acl docs per PR#901 * using semantic link breaks * Fix the example of `Format-Wide -ShowError` (#1851) * Fixed Test-ScriptFileInfo example (#1852) * fixing issue 1768 * Formatting, example fix for Body parameter (#1847) 1. Replaced variable names with PascalCase convention and for consistency 2. Removed directory information [c:\] in the examples 3. Put powershell keyword for formatting examples 4. Replaced Invoke-RestMethod with Invoke-WebRequest in the Body example, added method Post 5. Removed InformationAction and InformationVariable parameters, which were mistakenly a copy of Body, included already in CommonVariables part * fixing style consistency across articles * Fix example numbers in Resume-Job.md (#1857) Example 4 is duplicated. * Fixes typo $WebSiteName in separatingEnvData.md (#1856) - Adds the website name to common node property inside configuration data. - Also, it is now referenced (e.g. $Node.WebSiteName) in the DSC configuration document in MyWebApp.ps1. * Updates configurations.md (#1855) Two set of changes made. - Example scripts e.g. MyDscConfiguration.ps1 define the configuration inside them and call the configuration at the end line. Removed the call to the configuration at the end. Since the article demonstrates dot-sourcing the file and calling the configuration explicitly. - Fixed typo in the file name (TEST-PC1.mof to localhost.mof ), since the ComputerName was not specified it should default to using 'localhost' as the default argument for it. P.S. - There is a comment on the web-page regarding the fixes made * Fix typo in comment (#1854) * Updating the help content for v6. (#1853) * Updating the help content for v6. * Address code review comments * Fix broken links * Fix example numbers in about_Transactions.md (#1859) Example number '7' is duplicated. * Update Alias-Provider.md (#1831) 1. Removed statement that an alias is to an executable, the definition cotnains the path. It may - but does not need to be. For example: Try Set-Alias np Notepad then look at the definition. 2. Clarified that an alias can also be to a powershell script (ps1 file). 3. Tidied up the language removing multiple 'And,' clauses to improve readability. * Add documentation of new -AsHashtable switch for ConvertFrom-Json introduced by PR #5043 (#1858) * add documentation of new -AsHashTable switch for ConvertFrom-Json and also document the behaviour in case of duplicate strings. * correct casing of -AsHashtable switch. * Address PR comments about -AsHashtable switch for ConvertFrom-Json.md * Accept pipeline input: False for -AsHashtable switch in ConvertFrom-Json.md * Revert "Accept pipeline input: False for -AsHashtable switch in ConvertFrom-Json.md" Accidentally change the wrong field. This reverts commit 6e76191. * Accept pipeline input: False for -AsHashtable switch in ConvertFrom-Json.md * Fix example numbers in Invoke-WebRequest.md (#1862) Example number '4' is duplicated. * reformatting and integrating changes from PR#1831 (#1860) * Fix example numbers in Get-Help.md (#1869) Example number 12 and 13 are missing. * Fix example numbers in Import-Module.md (#1868) Example number '10' is duplicated. * Fix example number in ConvertTo-Html.html (#1867) Example number '10' is duplicated. * Update dscCiCd.md (#1865) Missing a period on line 378. Should be `$(Build.ArtifactStagingDirectory)\` not `$(BuildArtifactStagingDirectory)\`. * Web Cmdlets 6.0.0 Documentation Refresh (#1870) * Web Cmdlets 6.0.0 Documentation Refresh * Address PR Feedback * Merge Example 4 and 5 in Get-Member.md (#1874) Example 4 and 5 in Get-Member.md v3.0 and v4.0 are almost the same. They should be merged as with v5.0. * Remove hash algorithms unsupported in v6.0 (#1873) MACTripleDES and RIPEMD160 are no longer supported in v6.0. * Update outputs of Get-Verb (#1872) Since v6.0, `Get-Verb` returns not MemberDefinition but VerbInfo that has Verb and Group properties. * Fix typo in ConvertTo-Html.md (UTF-x) (#1879) * Fix "Accept wildcard characters" in Get-Service.md v6 (#1878) * Fixed "False" -> "True" (`DisplayName`, `Exclude`, `Include`, and `Name`) * Removed `InformationAction` and `InformationVariable` * Fixed Get-WindowsFeature cmdlet HyperLink (#1877) * Fixed Get-WindowsFeature cmdlet HyperLink Minor edit. Update Get-WindowsFeature cmdlet HyperLink to https://technet.microsoft.com/library/jj205469(v=wps.630).aspx * Changed URL to new docs.microsoft.com location The TechNet URL did not work. TechNet and MSDN are being retired. * Update Get-WinEvent.md (#1876) Removed future tense in a couple of places to improve readability. Minor edit. * Update Example 8 in Get-Process.md (find the owner of a process) (#1875) * Update Example 8 in Get-Process.md (Find the owner of a process) * Update to attempt to avoid build errors It seems that the build system does not accept multiple script blocks per one Example header. * updated localmachine\Root to LocalMachine\My (#1880) The example where we import the PFX on the target node should import the cert into Personal store and not root. * Update Group property example in Get-Verb.md (#1881) * adding missing space (#1885) * removing stray character (#1886) * Update Example 9 in Get-Process.md (#1888) * powershell -> pwsh (only v6.0) * Windows PowerShell -> PowerShell * Remove "About ISE" files of v6.0 (#1891) * Remove "About ISE" files of v6.0 ISE is no longer bundled with PowerShell 6.0. * Remove links for "About ISE" files of v6.0 * Update Get-Process.md (#1890) Fixed name parameter details to show it accepts wildcards in the name * Update productincompat.md (#1892) The list of compatible systems should include Skype For Business Server 2015 and Lync Server 2013. * Update unapproved verbs examples in Get-Verb.md (#1896) * Updated Example 4 * Removed Example 5 * Removing extra space in the Example 5A script (#1894) It was highlighting as string in the documentation, I was trying to remove all the extra space. * fixing merge conflict * updates to style and contrib * tweak format * tweak format 2 * fix typo * fix number list example * adding review feedback * fix broken links * incorporating feedback from zach * reformatting About_* for 80 columns - part 1 * reformat about_* * reformatting About_* topics - Part 2 * fixing broken links * fixing more broken links * more broken links fixed * Fix parameter's position in Get-Random.md (#1901) * Fix parameter's position in Measure-Command.md (#1905) * Fix parameter's position in Trace-Command.md (#1904) * Actually call the configuration in the example (#1906) On line 74, it says... "The last line of the example containing only the name of the configuration, calls the configuration." This change actually makes that call. * reformatting About_* for 80 columns - part 3 (#1902) * reformatting About_* * reformatting About_* part 3 * fixing broken links * fixing more broken links * one more time with the links * reformatting About_* for 80 columns - part 4 * Adding PreRelease versioning info for PSGallery & PSGet (#1903) * PowerShellGet PreRelease Support Adding descriptive doc for pre-release versioning support * Correcting typos in pre-release doc Minor typos and case issues fixed * Updated prerelease info based on feedback Mostly cosmetic updates. Functional change: added line 28, stating we only support 3-segment module versions. * Adding prerelease to module install update find save commands * Updating PSGet -Script commands for Prerelease support * Hyphen listed as optional rather than preferred in Prereleasestring * Minor corrections from Rebro review * Addressing @sdwheeler feedback on links and double slashes * Fixing broken link * Update PreReleaseScript.md * Style tweaks in STYLE.md (#1913) * Fix YAML metadata on "Understanding Concepts" (#1911) I'm not quite sure what this means, but it certainly looks terrible on docs.microsoft.com when it's malformed. (To be perfectly honest, I only managed to even figure out it's called "YAML metadata" by peeking at the DOM of github's HTML.) * Fix parameter's position in Join-Path.md (#1909) * typo correction on line 85 (#1916) E:\Windows\Sytem32 sould be E:\Windows\System32 * Fix parameter's position in Get-TraceSource.md (#1917) * Changed required PSGet version to 1.6.0 (#1920) * Update Example 5 in Get-Process.md (#1923) * fixing backlashes reported in PR1921 (#1924) * fixing backlashes reported in PR1921 * found more backslashes
1 parent 7bb75bf commit 58371ab

File tree

72 files changed

+6039
-6414
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

72 files changed

+6039
-6414
lines changed

contributing/STYLE.md

Lines changed: 7 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,8 @@ Basic formatting guidelines:
2424

2525
- Limit lines to 80 characters
2626
- Code blocks should be limited to 76 characters
27-
- Within a paragraph, the following characters must be escaped using a leading `\` character: $,\`,\<
27+
- Within a paragraph, the following characters must be escaped using a leading `\` character:
28+
<code>$</code>, <code>\`</code>, <code>\<</code>
2829
- Tables need fit withing 76 characters
2930
- Manually wrap contents of cells across multiple lines
3031
- Use opening and closing `|` characters on each line
@@ -59,13 +60,13 @@ Remove extra spaces at the end of lines.
5960

6061
## Titles/Headings
6162

62-
Only use [ATX headings][atx] (as opposed to = or \- style headers).
63+
Only use [ATX headings][atx] (# style, as opposed to = or \- style headers).
6364

6465
* Titles/headings should be surrounded by blank lines
6566
* Only the first letter of a title and any proper nouns in that title should be capitalized
6667
* Only one H1 per document
6768

68-
When editing reference content, the H2s are prescribed by platyPS and must not be added or removed.
69+
When editing reference content, the H2s are prescribed by [platyPS][platyPS] and must not be added or removed.
6970
Adding or removing H2 causes a build break.
7071

7172
## Formatting syntax elements
@@ -85,7 +86,7 @@ Adding or removing H2 causes a build break.
8586

8687
## Formatting code blocks
8788

88-
* All PowerShell syntax blocks should use &#96;&#96;&#96;powershell code fence marker.
89+
* All PowerShell syntax blocks should use <code>\`\`\`powershell</code> &hellip; <code>\`\`\`</code> code fence markers.
8990

9091
* Do **NOT** start PowerShell commands with the PowerShell prompt ("`PS C:\>`").
9192

@@ -168,4 +169,5 @@ There are special rules for linking to reference topics from conceptual topics.
168169
[about-example]: https://github.com/PowerShell/PowerShell-Docs/blob/staging/reference/5.1/Microsoft.PowerShell.Core/About/about_Comparison_Operators.md
169170
[links]: https://help.github.com/articles/relative-links-in-readmes/
170171
[gfm-spec]: https://github.github.com/gfm/
171-
[semantics]: http://rhodesmill.org/brandon/2012/one-sentence-per-line/
172+
[semantics]: http://rhodesmill.org/brandon/2012/one-sentence-per-line/
173+
[platyPS]: https://github.com/PowerShell/platyPS

dsc/bootstrapDsc.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -82,7 +82,7 @@ Configuration SampleIISInstall
8282
Rename and move that file into the proper location on the VHD as `Pending.mof` by using the [Move-Item](https://technet.microsoft.comlibrary/hh849852.aspx) cmdlet. For example:
8383
8484
```powershell
85-
Move-Item -Path C:\DSCTest\SampleIISInstall\localhost.mof -Destination E:\Windows\Sytem32\Configuration\Pending.mof
85+
Move-Item -Path C:\DSCTest\SampleIISInstall\localhost.mof -Destination E:\Windows\System32\Configuration\Pending.mof
8686
```
8787
6. Dismount the VHD by calling the [Dismount-VHD](https://technet.microsoft.com/library/hh848562.aspx) cmdlet. For example:
8888
Lines changed: 200 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,200 @@
1+
---
2+
ms.date: 2017-09-26
3+
contributor: keithb
4+
ms.topic: reference
5+
keywords: gallery,powershell,cmdlet,psget
6+
title: PrereleaseModule
7+
---
8+
9+
# Prerelease Module Versions
10+
Starting with version 1.6.0, PowerShellGet and the PowerShell Gallery provide support for tagging versions greater than 1.0.0 as a prerelease. Prior to this feature, prerelease items were limited to having a version beginning with 0. The goal of these features is to provide greater support for [SemVer v1.0.0](http://semver.org/spec/v1.0.0.html) versioning convention without breaking backwards compatibility with PowerShell versions 3 and above, or existing versions of PowerShellGet. This topic focuses on the module-specific features. The equivalent features for scripts are in the [Prerelease Versions of Scripts](../script/PrereleaseScript.md) topic. Using these features, publishers can identify a module or script as version 2.5.0-alpha, and later release a production-ready version 2.5.0 that supersedes the prerelease version.
11+
12+
At a high level, the prerelease module features include:
13+
14+
* Adding a Prerelease string to the PSData section of the module manifest identifies the module as a prerelease version.
15+
When the module is published to the PowerShell Gallery, this data is extracted from the manifest, and used to identify prerelease items.
16+
* Acquiring prerelease items requires adding -AllowPrerelease flag to the PowerShellGet commands Find-Module, Install-Module, Update-Module, and Save-Module.
17+
If the flag is not specified, prerelease items will not be shown.
18+
* Module versions displayed by Find-Module, Get-InstalledModule, and in the PowerShell Gallery will be displayed as a single string with the Prerelease string appended, as in 2.5.0-alpha.
19+
20+
Details for the features are included below.
21+
22+
These changes do not affect the module version support that is built into PowerShell, and are compatible with PowerShell 3.0, 4.0, and 5.
23+
24+
## Identifying a module version as a prerelease
25+
26+
PowerShellGet support for prerelease versions requires the use of two fields within the Module Manifest:
27+
28+
* The ModuleVersion included in the module manifest must be a 3-part version if a prerelease version is used, and must comply with existing PowerShell versioning. The version format would be A.B.C, where A, B, and C are all integers.
29+
* The Prerelease string is specified in the module manifest, in the PSData section of PrivateData.
30+
Detailed requirements on the Prerelease string are below.
31+
32+
An example section of a module manifest that defines a module as a prerelease would look like the following:
33+
```powershell
34+
@{
35+
ModuleVersion = '2.5.0'
36+
#---
37+
PrivateData = @{
38+
PSData = @{
39+
Prerelease = 'alpha'
40+
}
41+
}
42+
}
43+
```
44+
45+
The detailed requirements for Prerelease string are:
46+
47+
* Prerelease string may only be specified when the ModuleVersion is 3 segments for Major.Minor.Build. This aligns with SemVer v1.0.0.
48+
* A hyphen is the delimiter between the Build number and the Prerelease string. A hyphen may be included in the Prerelease string as the first character, only.
49+
* The Prerelease string may contain only ASCII alphanumerics [0-9A-Za-z-]. It is a best practice to begin the Prerelease string with an alpha character, as it will be easier to identify that this is a prerelease version when scanning a list of items.
50+
* Only SemVer v1.0.0 prerelease strings are supported at this time. Prerelease string __must not__ contain either period or + [.+], which are allowed in SemVer 2.0.
51+
* Examples of supported Prerelease string are: -alpha, -alpha1, -BETA, -update20171020
52+
53+
__Prerelease versioning impact on sort order and installation folders__
54+
55+
Sort order changes when using a prerelease version, which is important when publishing to the PowerShell Gallery, and when installing modules using PowerShellGet commands.
56+
If the Prerelease string is specified for two modules, the sort order is based on the string portion following the hyphen. So, version 2.5.0-alpha is less than 2.5.0-beta, which is less than 2.5.0-gamma.
57+
If two modules have the same ModuleVersion, and only one has a Prerelease string, the module without the Prerelease string is assumed to be the production-ready version and will be sorted as a greater version than the prerelease version (which includes the Prerelease string).
58+
As an example, when comparing releases 2.5.0 and 2.5.0-beta, the 2.5.0 version will be considered the greater of the two.
59+
60+
When publishing to the PowerShell Gallery, by default the version of the module being published must have a greater version than any previously-published version that is in the PowerShell Gallery.
61+
62+
## Finding and acquiring prerelease items using PowerShellGet commands
63+
64+
Dealing with prerelease items using PowerShellGet Find-Module, Install-Module, Update-Module, and Save-Module commands requires adding the -AllowPrerelease flag.
65+
If -AllowPrerelease is specified, prerelease items will be included if they are present.
66+
If -AllowPrerelease flag is not specified, prerelease items will not be shown.
67+
68+
The only exceptions to this in the PowerShellGet module commands are Get-InstalledModule, and some cases with Uninstall-Module.
69+
70+
* Get-InstalledModule always will automatically show the prerelease information in the version string for modules.
71+
* Uninstall-Module will by default uninstall the most recent version of a module, if __no version__ is specified. That behavior has not changed. However, if a prerelease version is specified using -RequiredVersion, -AllowPrerelease will be required.
72+
73+
## Examples
74+
```powershell
75+
# Assume the PowerShell Gallery has TestPackage module versions 1.8.0 and 1.9.0-alpha. If -AllowPrerelease is not specified, only version 1.8.0 will be returned.
76+
C:\windows\system32> find-module TestPackage
77+
78+
Version Name Repository Description
79+
------- ---- ---------- -----------
80+
1.8.0 TestPackage PSGallery Package used to validate changes to the PowerShe...
81+
82+
C:\windows\system32> find-module TestPackage -AllowPrerelease
83+
84+
Version Name Repository Description
85+
------- ---- ---------- -----------
86+
1.9.0-alpha TestPackage PSGallery Package used to validate changes to the PowerShe...
87+
88+
# To install a prerelease, always specify -AllowPrerelease. Specifying a prerelease version string is not sufficient.
89+
90+
C:\windows\system32> Install-module TestPackage -RequiredVersion 1.9.0-alpha
91+
PackageManagement\Find-Package : No match was found for the specified search criteria and module name 'TestPackage'.
92+
Try Get-PSRepository to see all available registered module repositories.
93+
At C:\Program Files\WindowsPowerShell\Modules\PowerShellGet\1.6.0\PSModule.psm1:1455 char:3
94+
+ PackageManagement\Find-Package @PSBoundParameters | Microsoft ...
95+
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
96+
+ CategoryInfo : ObjectNotFound: (Microsoft.Power...ets.FindPackage:FindPackage) [Find-Package], Exceptio
97+
n
98+
+ FullyQualifiedErrorId : NoMatchFoundForCriteria,Microsoft.PowerShell.PackageManagement.Cmdlets.FindPackage
99+
100+
# The previous command failed because -AllowPrerelease was not specified.
101+
# Adding -AllowPrerelease will result in success.
102+
103+
C:\windows\system32> Install-module TestPackage -RequiredVersion 1.9.0-alpha -AllowPrerelease
104+
C:\windows\system32> Get-InstalledModule TestPackage
105+
106+
Version Name Repository Description
107+
------- ---- ---------- -----------
108+
1.9.0-alpha TestPackage PSGallery Package used to validate changes to the PowerShe...
109+
110+
```
111+
112+
Side-by-side installation of versions of a module that differ only due to the prerelease specified is not supported.
113+
When installing a module using PowerShellGet, different versions of the same module are installed side-by-side by creating a folder name using the ModuleVersion.
114+
The ModuleVersion, without the prerelease string, is used for the folder name.
115+
If a user installs MyModule version 2.5.0-alpha, it will be installed to the MyModule\2.5.0 folder.
116+
If the user then installs 2.5.0-beta, the 2.5.0-beta version will __over-write__ the contents of the folder MyModule\2.5.0.
117+
One advantage to this approach is that there is no need to un-install the prerelease version after installing the production-ready version.
118+
The example below shows what to expect:
119+
120+
121+
``` powershell
122+
C:\windows\system32> Get-InstalledModule TestPackage -AllVersions
123+
124+
Version Name Repository Description
125+
------- ---- ---------- -----------
126+
1.9.0-alpha TestPackage PSGallery Package used to validate changes to the PowerShe...
127+
1.8.0 TestPackage PSGallery Package used to validate changes to the PowerShe...
128+
1.1.3.2 TestPackage PSGallery Package used to validate changes to the PowerShe...
129+
130+
C:\windows\system32> find-module TestPackage -AllowPrerelease
131+
132+
Version Name Repository Description
133+
------- ---- ---------- -----------
134+
1.9.0-beta TestPackage PSGallery Package used to validate changes to the PowerShe...
135+
136+
C:\windows\system32> Update-Module TestPackage -AllowPrerelease
137+
C:\windows\system32> Get-InstalledModule TestPackage -AllVersions
138+
139+
Version Name Repository Description
140+
------- ---- ---------- -----------
141+
1.9.0-beta TestPackage PSGallery Package used to validate changes to the PowerShe...
142+
1.8.0 TestPackage PSGallery Package used to validate changes to the PowerShe...
143+
1.1.3.2 TestPackage PSGallery Package used to validate changes to the PowerShe...
144+
145+
```
146+
147+
Uninstall-Module will remove the latest version of a module when -RequiredVersion is not supplied.
148+
If -RequiredVersion is specified, and is a prerelease, -AllowPrerelease must be added to the command.
149+
150+
``` powershell
151+
C:\windows\system32> Get-InstalledModule TestPackage -AllVersions
152+
153+
Version Name Repository Description
154+
------- ---- ---------- -----------
155+
2.0.0-alpha1 TestPackage PSGallery Package used to validate changes to the PowerShe...
156+
1.9.0-beta TestPackage PSGallery Package used to validate changes to the PowerShe...
157+
1.8.0 TestPackage PSGallery Package used to validate changes to the PowerShe...
158+
1.1.3.2 TestPackage PSGallery Package used to validate changes to the PowerShe...
159+
160+
C:\windows\system32> Uninstall-Module TestPackage -RequiredVersion 1.9.0-beta
161+
Uninstall-Module : The '-AllowPrerelease' parameter must be specified when using the Prerelease string in
162+
MinimumVersion, MaximumVersion, or RequiredVersion.
163+
At line:1 char:1
164+
+ Unnstall-Module TestPackage -RequiredVersion 1.9.0-beta
165+
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
166+
+ CategoryInfo : InvalidArgument: (:) [Uninstall-Module], ArgumentException
167+
+ FullyQualifiedErrorId : AllowPrereleaseRequiredToUsePrereleaseStringInVersion,Uninnstall-Module
168+
169+
170+
171+
C:\windows\system32> Uninstall-Module TestPackage -RequiredVersion 1.9.0-beta -AllowPrerelease
172+
C:\windows\system32> Get-InstalledModule TestPackage -AllVersions
173+
174+
Version Name Repository Description
175+
------- ---- ---------- -----------
176+
2.0.0-alpha1 TestPackage PSGallery Package used to validate changes to the PowerShe...
177+
1.8.0 TestPackage PSGallery Package used to validate changes to the PowerShe...
178+
1.1.3.2 TestPackage PSGallery Package used to validate changes to the PowerShe...
179+
180+
C:\windows\system32> Uninstall-Module TestPackage
181+
C:\windows\system32> Get-InstalledModule TestPackage -AllVersions
182+
183+
Version Name Repository Description
184+
------- ---- ---------- -----------
185+
1.8.0 TestPackage PSGallery Package used to validate changes to the PowerShe...
186+
1.1.3.2 TestPackage PSGallery Package used to validate changes to the PowerShe...
187+
188+
189+
```
190+
191+
192+
193+
## More details
194+
### [Prerelease Script Versions](../script/PrereleaseScript.md)
195+
### [Find-Module](./psget_find-module.md)
196+
### [Install-Module](./psget_install-module.md)
197+
### [Save-Module](./psget_save-module.md)
198+
### [Update-Module](./psget_update-module.md)
199+
### [Get-InstalledModule](./psget_get-installedmodule.md)
200+
### [UnInstall-Module](./psget_uninstall-module.md)

gallery/psget/module/psget_find-module.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -63,6 +63,9 @@ Find-Module -Name PSReadline -MinimumVersion 1.0.0.12 -MaximumVersion 1.0.0.13
6363
# Find a module with exact version
6464
Find-Module -Name AzureRM -RequiredVersion 1.3.2
6565
66+
# Find a module with a specific prerelease version
67+
Find-Module -Name AzureRM -RequiredVersion 1.3.2-alpha -AllowPrerelease
68+
6669
# Find a module from the specified repository
6770
Find-Module -Name Contoso -Repository MyLocalRepo
6871

gallery/psget/module/psget_install-module.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -77,6 +77,12 @@ Install-Module -Name ContosoServer -MinimumVersion 1.0
7777
# Install a specific version of a module
7878
Install-Module -Name ContosoServer -RequiredVersion 1.1.3
7979
80+
# Install a specific prerelease version of a module
81+
Install-Module -Name ContosoServer -RequiredVersion 1.1.3-alpha -AllowPrerelease
82+
83+
# Install the latest version of a module by name, including prelrelease versions if one exists
84+
Install-Module -Name ContosoServer -AllowPrerelease
85+
8086
# Install the latest version of a module to $home\Documents\WindowsPowerShell\Modules.
8187
Install-Module -Name ContosoServer -Scope CurrentUser
8288

gallery/psget/module/psget_save-module.md

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -50,5 +50,14 @@ Find-Command -Name "Get-NestedRequiredModule4" -Repository "INT" | Save-Module -
5050
# Save the role capability modules by piping the Find-RoleCapability output to Save-Module cmdlet.
5151
Find-RoleCapability -Name Maintenance,MyJeaRole | Save-Module -Path C:\MyModulesPath
5252
53+
54+
# Save a specific prerelease version of a module to C:\MySavedModuleLocation
55+
Save-Module -Name ContosoServer -RequiredVersion 1.1.3-alpha -Path C:\MySavedModuleLocation -AllowPrerelease
56+
57+
# Install the latest version of a module by name, including prelrelease versions if one exists
58+
Install-Module -Name ContosoServer -Path C:\MySavedModuleLocation -AllowPrerelease
59+
60+
61+
5362
```
5463

0 commit comments

Comments
 (0)