Skip to content

Commit

Permalink
Merge latest changes into live (#2092)
Browse files Browse the repository at this point in the history
* 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

* reformatting About_* for 80 columns - part 5

* reformatting About_* for 80 columns - part 6

* incorporating review feedback

* reformatting About_* for 80 columns - part 7

* Fixed formatting of output per issue #808

* Fix typo in syntax description (#1931)

* Fix parameter's position in ConvertTo-Xml.md (#1929)

* Remove descriptions about ComputerName parameter in Get-Process.md v6.0 (#1928)

* Line 192  Single Quote Breaks Example (#1930)

* Line 192  Single Quote Breaks Example

* clarified the example for -Regex

* Update Example 2 in Get-Alias.md (ineffective Exclude) (#1935)

`-Exclude Get-*` is ineffective because there are no aliases that begin with `Get-`.

* Fix formatting: DESCRIPTION section in ConvertTo-Xml.md (#1934)

* Fix typo in Unregister-ScheduledJob (#1932)

* Update Unregister-ScheduledJob.md

* Update Unregister-ScheduledJob.md

* Update Unregister-ScheduledJob.md

* Update Unregister-ScheduledJob.md

* Fix parameter's position in ConvertFrom-Csv.md (#1937)

* fix typo on metaConfig.md (#1936)

fixed typo

* Quick edits (#1938)

* Changed required PSGet version to 1.6.0

* Fixes to PSGet TOC and WMF 5.1 compat page

* Update Get-Item.md (#1942)

Proof-read some of the examples. The first two were wrong entirely: The user must be in the ps-test folder for the result shown to happen.

* Add description about Format-Hex -InputObject (#1939)

* Fix parameter's position in Add-Member.md (#1946)

* Fix parameter's position in Select-Object.md (#1945)

* Correcting add to hash table example (#1944)

* Update about_Hash_Tables.md

corrected add to hash table example in 3.0

* Update about_Hash_Tables.md

corrected add to hash table examples in 4.0

* Update about_Hash_Tables.md

corrected add to hash table example in 5.0

* Update about_Hash_Tables.md

corrected add to hash table example in 5.1

* Update about_Hash_Tables.md

corrected add to hash table example in 6

* Fix Set-TraceSource -ListenerOption parameter (#1949)

* Fixed the value of "Accepted values:"
* Fixed minor differences in formatting and wording

* Fix Trace-Command -ListenerOption parameter (#1948)

* Fixed the value of "Accepted values:"
* Fixed minor differences in formatting and wording

* Fix parameter's position in Select-Xml.md (#1953)

* Fix Get-Alias -Name parameter (#1952)

* Position: 0
* Default value: All aliases
* Accept wildcard characters: True
* Fixed minor differences in formatting and wording

And also removed InformationAction/InformationVariable in v6.0.

* Wmf 5.1 cleanup (#1950)

* Changed required PSGet version to 1.6.0

* Fixes to PSGet TOC and WMF 5.1 compat page

* Add note explaining WMF does not ship in Windows

* Typo fix ("you will are not" -> "you will not"). (#1951)

* Typo fix ("you will are not" -> "you will not").

* Changed from passive voice to active voice

* added article about formatting code samples

* fixing typos

* fixed typos and incorporated feedback

* updating metadata tags in docfx.json

* fixing filename spelling

* Fix parameter's position in Get-Content.md (#1959)

* Fix parameter's position in Get-Member.md (#1958)

* Update PSGallery "Items Tab" (for the new prerelease feature) (#1957)

* Fix link for about_WorkflowCommonParameters in New-PSWorkflowExecutionOption.md (#1962)

* Fix link for about_Types.ps1xml in Update-TypeData.md (#1961)

* Fix parameter's position in Group-Object.md (#1966)

* Fix hex values in about_Arithmetic_Operators.md (#1965)

* Indent headers as subheaders (#1967)

* Update minor typo in Limit-EventLog.md (#1968)

* Update Example 3 in Get-FileHash.md (#1969)

* Fix parameter's position in Tee-Object.md (#1970)

* fixing output example per issue 1933

* fix -Path metadata to reflect wildcard support

* fixing issue 1640

* fixing issue 1651

* Fix link for about_Remote_Requirements (#1976)

* Split parameter set in Sort-Object.md v6.0 (#1975)

Since v6.0, Sort-Object cmdlet has two parameter sets, "Default" and "Bottom".

* Fix link for about_Preference_Variables (#1982)

http://... -> relative path

* Fix broken headers in Get-CimSession.md v6.0 (#1981)

* Update Example 1 in Import-Counter.md (#1980)

* move $OFS to prefs article added note about read-only (#1978)

* Update decisionMaker.md (#1984)

Slight, but critical corrections to the definition of DevOps.

* Update configurations.md (#1985)

* Fix parameter's position in Restart-Service.md (#1993)

* Fix link for logical operators in about_Operator_Precedence.md (#1992)

* Update scriptResource.md (#1986)

Match specified GetScript rule

* Bad link (#1988)

The link "http://go.microsoft.com/fwlink/?LinkId=119096" is supposed to point to a page or a document about "Code-Signing Best Practices".
However, it points to a video about "Understanding Extension INFs and Component INFs".
I watched the whole video and there is nothing inside about "Code-Signing Best Practices".
The best match I have found is the following one: http://download.microsoft.com/download/a/f/7/af7777e5-7dcd-4800-8a0a-b18336565f5b/best_practices.doc
It would be a very good idea to make a web page from this document. Pieces of advice it contains are still accurate.

* Update Example 1 of Protect-CmsMessage (#1987)

The existing example did not specify you needed to create the INF. This not only says so but does so using a script block piped to out-file

* Small edits for mispellings (#1989)

* Corrected command (#1990)

The CanPauseAndContinue property is a boolean so the correct comparison to use is $true rather than "True".

* removing module ref for modules that do not ship in v6-rc2 (#1996)

* Fix parameter's position in Resume-Service.md (#1998)

* Fix link for about_Providers (#1999)

* Help doc enhancement for ConvertFrom-StringData cmdlet (#2002)

* Help doc correction

Removed an unwanted * from Notes section

Corrected intenting for last example

Removed unwanted ... from example 2

* Help doc wnhancements in all versions for ConvertFrom-StringData

Removed an unwanted * from Notes section

Corrected intenting for last example

Removed unwanted ... from example 2

* PowerShell 6 logging on Windows, Linux, and MacOS (#1922)

* First draft of PowerShell 6 logging

* Fix style guideline issues.

* Document logging settings in PowerShellProperties.json

* Address PR Feedback
Limit lines to 80 columns, when possible
Insert <br> in selected locations to improve readability of rendered markdown.

* Reformatted tables

Reformatted tables to work with new processing of About_* topics

* Adding calling the ComputerName parameter to the example (#1964)

* Adding calling the ComputerName parameter to the example

* Changing quotes to brackets

* Removed unused variable in Example 1 (#2004)

The variable was declared but not used.  It also appears in the same place in Example 2 but is used later on.

* Made surrounding text agree with sample code. (#2003)

* Reformatting v4 About_ topics missed in first pass (#2006)

* v4 about scrub missed files

* fixing broken links

* fix broken link

* Reformatting v3 About_ topics missed in first pass (#2005)

* v3 about scrub missed files

* fixing broken links

* fix broken link

* Reformatting v5 About_ topics missed in first pass (#2008)

* v5 about scrub missed files

* fixing broken links

* v5.1 about scrub missed files (#2009)

* Reformatting v6 About_ topics missed in first pass (#2010)

* v6 about scrub missed files

* fixing broken links and removing non-v6 content

* final pass on About_ topic reformat (#2011)

* Corrected Example 3 (#2014)

* Corrected Example 3

Example 3 is an example to remove the user from the group but instead it was removing the group completely.  This change adds the correct syntax to perform what was intended.

See #2001

* minor edits for spacing and metadata

* Enable running pandoc on about topic files (#2012)

* Enable running pandoc on about topic files

* Remove extra line

* Removed --ascii parameter from pandoc as it is not required

* Creates output directory as pandoc needs it (#2018)

* remove alias `sc` to match PSCore6 (#2021)

* Cmdlet help for ConvertFrom-Clixml and ConvertTo-Clixml  (#2022)

* Cmdlet help for ConvertFrom-Clixml and ConvertTo-Clixml for Powershell#3898

* minor edits

- Removed -information* common parameters
- reformat code blocks
- renumbered example

* minor updates

- reformatted examples
- removed common paramters

* update link to about topic

* minor edits

- removed common parameters
- formatted code blocks

* minor edits

- reformatted code blocks
- removed common parameters

* fix broken link (#2024)

* Adding more info to Contributor Guide (#2023)

* adding notes about OPS extensions

* added notes about OPS extensions and linking

* fix typo

* fix typo

* Support lifecycle doc (#1994)

* first pass of support lifecycle doc

* add notes on MIT license

* address slee's comments on support lifecycle

* respond to lifecycle feedback from Sean

* add lifecycle image

* Fixed spelling typo

* add lifecycle to TOC

* respond to feedback on lifecycle

* Removed en-us from URLs

You need to remove locale paths from URLs. Including en-us forces the reader to English rather than being redirected to the localized version of the article that matches their locale.

* add note on 12 months, fix en-us

* Fixed typo

* Move setup/install and remoting docs into PowerShell-Docs (#2026)

This creates a couple new topics around WSMan remoting, SSH remoting, and installing/configuring PowerShell Core. It also adds a topic on using VS Code with PowerShell.

* PowerShell Core 6.0 release notes (#2020)

What's New in PowerShell Core 6.0

* update TOC and change title of setup mac/linux article (#2030)

* update TOC and change title of setup mac/linux article

* fix typos

* attempt to fix images (#2033)

* attempt to fix images

* update to docfx to support images

* Update docfx to add image support (#2040)

* attempt to fix images

* update to docfx to support images

* update root docfx for images

* update docfx for image support

* Update Installing-PowerShell-Core-on-Windows.md (#2042)

The original paged rendered badly - this edit is a move of a 'to do' comment in the MD so as to not break the sentence.

* Fix $PSVersionTable.OS in What's New 6.0 (#2039)

$PSVersionTable.OS is:
x [System.Environment]::OSVersion.VersionString
o [System.Runtime.InteropServices.RuntimeInformation]::OSDescription

* Update WSMan-Remoting-in-PowerShell-Core.md (#2038)

The current example doesn't work for me when specifying the full file path.  It just outputs the file location rather than running the script.  I had to move to the location of the file and run it from there.

The parameter PowerShellVersion also doesn't appear to exist anymore so I have removed that.  

I've also changes file paths to match the 6.0.0 GA release rather than the previous alpha 9.

* Update Get-FormatData.md (#2034)

Updated Get-FormatData Markdown.  Fixes #1895

* Update Get-FormatData Markdown (#2035)

Updated Get-FormatData Markdown.  Fixes #1895

* Updated Get-Runspace Help (#2032)

Updated Get-Runspace Markdown.  Fixes #1883

* updated docfx to try to fix images (#2043)

* attempt to fix images

* update to docfx to support images

* update root docfx for images

* update docfx for image support

* update docfx for images

* Add resource per version in docfx.json (#2046)

* Change 'PowerShellProperties.json' to 'powershell.config.json' in about_logging (#2050)

* OPS Build config changes and minor article edits (#2051)

* clean up warnings from build log

* clean up moniker mapping and add image types to config

* removing unneeded index pages

* fixing typos

* Update New-PSSessionOption.md (#2052)

Missing "are" between "they" and "effective".

* Update Add-Member.md example layouts (#2055)

* Update Add-Member.md

fixed layout of examples 1,2 ,3

* fixed format of example 5

* Removes unnecessary description about the RunAsAdministrator parameter (#2057)

There is no need to have documentation for functions which do not exists in the product.
There is no need to specify in which version this feature was added. Otherwise we need to add such remarks to many other features as well

* Fix Example 2 in Set-PSReadlineKeyHandler.md (#2058)

* Fix Example 1 in Remove-PSReadlineKeyHandler.md (#2059)

* Fix minor Markdown syntax error (#2060)

"Backwards compatibility with Windows PowerShell" anchor reference had incorrect Markdown syntax.

* Update secureMOF.md (#2061)

Update "On the Target Node: create and export the certificate" section

* remove eric and jp from metadata

* update docs to reflect change by https://github.com/PowerShell/PowerShell/pull/5923y (#2064)

* Fix release links/names (6.0.0) (#2056)

Corrected links and names to match the 6.0.0 release

* Removes unexistent RunAsAdministrator parameter from the Syntax section (#2066)

* Fixed path inconsistencies in Set-ItemProperty Example 2 (#2072)

* Corrected path error in Example 2

* Corrected path error in Example 2

* Corrected error in Example 2

* Updated About documentation links to relative paths (#2071)

* Gallery ui manifest (#2073)

* Changed required PSGet version to 1.6.0

* New doc explaining how manifests affect Gallery UI

* Adding new topic to TOC

* Escapes angle brackets in about_Requires (#2075)

This change makes content in this brackets displayable

* add links for topics

* About_Windows_PowerShell_5.1 #1171

* fix typo

* about_Type_Operators issues #1915

* fix typos

* add note about reboot (#2076)

* Removed empty bullet point below notes. (#2078)

A minor typo.

* change PowerShellProperties.json to powershell.config.json (#2079)

* Update metaConfig.md (#2081)

* Update metaConfig.md

* Update metaConfig.md

* Fix typo in code example (#2082)

* Fix example VB code (#2084)

* Fix example VB code

This VB code writen in a line is not compilable. `VBFromFilePublic` also requires a space.

* Fix example 4 VB code for all versions

* Remove the mentioning of version 2.0

* Adds missing SslProtocol parameter from Invoke-WebRequest cmdlet. (#2085)

* Add SslProtocol parameter.

* Add libcurl note to Certificate parameter.

* Import-Csv Update examples, and UseCulture (#2086)

* address example formatting
Also includes some update to wording that I'll expand on in PR.

* Start on update formatting for 3.0 doc

* More formatting

* Correcting examples and format of them.

* 3.0 update format example 1

* 3.0 update to example 2

* 3.0 update example 4

* 4.0 update example 1-4

* 5.0 update example 3 and 4

* 5.1 update example 4 paragraph format

* 3.0 update example 5

* 4.0 update example 5

* 5.0 update example 5

* 5.1 update example 5

* 5.1 update example 6

* 5.0 update example 6

* 4.0 update example 6

* 3.0 update example 6

* 3.0 update format of param Delimiter and Encoding

* 4.0 update format of param Delimiter and Encoding

* 5.0 update format of param Encoding

* 5.1 update format of param Encoding

* 5.0 update param header

* 4.0 update param header info

* 3.0 update param header info

* 5.1 update remaining parameter format

* 5.0 update remaining parameter format

* 4.0 update remaining parameter format

* 3.0 update remaining parameter format

* 3.0 update remaining parameter format

* 5.1 update notes format and add related link

* 5.0 update notes format and add related link

* 4.0 update notes format and add related link

* 3.0 update notes format and add related link

* update to example 1 across 3.0 to 5.1

* 6.0 Updates to description and example 1

* 4.0 update to example 1

* 3.0 - 5.1 update case of file name

* 6.0 update example 2 and 3

* 3.0 - 5.1 update case of file name

* 6.0 working on updating example 4
This example does not give same results I have on 6.0.1. Think other examples are going to be bad as well, have to go back and test those.

* update example 4

* update example 5

* 6.0 example 6 and parameter format

* addtional touchups on format

* Use a working URL in Clipboard examples (#2087)

* Fixed bad link in about_Hash_Tables.md docs (#2090)

Links to about_Object_Creation.md were malformed in all references versions.

* restoring changes made in PR#1870 (#2089)
  • Loading branch information
Sean Wheeler authored Feb 2, 2018
1 parent a444406 commit 18e3bfa
Show file tree
Hide file tree
Showing 44 changed files with 1,632 additions and 1,403 deletions.
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ Each folder in this repo publishes to [MSDN](https://msdn.microsoft.com/en-us/po
* [/dsc/](https://msdn.microsoft.com/en-us/powershell/dsc/) is for the Desired State Configuration feature
* [/gallery/](https://msdn.microsoft.com/powershell/gallery) is for the [PowerShell Gallery](https://www.powershellgallery.com/)
* [/jea/](https://msdn.microsoft.com/powershell/jea/) is for the Just Enough Administration feature
* [/reference/](https://msdn.microsoft.com/powershell/reference/) is for PowerShell module reference across versions 2.0, 3.0, 4.0, 5.0, 5.1, and 6.0
* [/reference/](https://msdn.microsoft.com/powershell/reference/) is for PowerShell module reference across versions 3.0, 4.0, 5.0, 5.1, and 6.0
* This content will be retrieved by the `Get-Help` cmdlet in the future
* [/scripting/](https://msdn.microsoft.com/en-us/powershell/scripting/) is general PowerShell reference content
* [/wmf](https://msdn.microsoft.com/en-us/powershell/wmf/readme) contains release notes for the Windows Management Framework, the package used to distribute new versions of PowerShell to previous versions of Windows.
Expand Down
2 changes: 1 addition & 1 deletion dsc/authoringResourceComposite.md
Original file line number Diff line number Diff line change
Expand Up @@ -197,7 +197,7 @@ To access the user context from within a custom resource, you can use the automa
For example the following code would write the user context under which the resource is running to the verbose output stream:

```powershell
if (PsDscContext.RunAsUser) {
if ($PsDscContext.RunAsUser) {
Write-Verbose "User: $PsDscContext.RunAsUser";
}
```
Expand Down
2 changes: 1 addition & 1 deletion dsc/metaConfig.md
Original file line number Diff line number Diff line change
Expand Up @@ -81,7 +81,7 @@ The following properties are available in a **Settings** block.
| CertificateID| string| The thumbprint of a certificate used to secure credentials passed in a configuration. For more information see [Want to secure credentials in Windows PowerShell Desired State Configuration](http://blogs.msdn.com/b/powershell/archive/2014/01/31/want-to-secure-credentials-in-windows-powershell-desired-state-configuration.aspx)?. <br> __Note:__ this is managed automatically if using Azure Automation DSC pull service.|
| ConfigurationDownloadManagers| CimInstance[]| Obsolete. Use __ConfigurationRepositoryWeb__ and __ConfigurationRepositoryShare__ blocks to define configuration pull service endpoints.|
| ConfigurationID| string| For backwards compatibility with older pull service versions. A GUID that identifies the configuration file to get from a pull service. The node will pull configurations on the pull service if the name of the configuration MOF is named ConfigurationID.mof.<br> __Note:__ If you set this property, registering the node with a pull service by using __RegistrationKey__ does not work. For more information, see [Setting up a pull client with configuration names](pullClientConfigNames.md).|
| ConfigurationMode| string | Specifies how the LCM actually applies the configuration to the target nodes. Possible values are __"ApplyOnly"__,__"ApplyandMonitior"__, and __"ApplyandAutoCorrect"__. <ul><li>__ApplyOnly__: DSC applies the configuration and does nothing further unless a new configuration is pushed to the target node or when a new configuration is pulled from a service. After initial application of a new configuration, DSC does not check for drift from a previously configured state. Note that DSC will attempt to apply the configuration until it is successful before __ApplyOnly__ takes effect. </li><li> __ApplyAndMonitor__: This is the default value. The LCM applies any new configurations. After initial application of a new configuration, if the target node drifts from the desired state, DSC reports the discrepancy in logs. Note that DSC will attempt to apply the configuration until it is successful before __ApplyAndMonitor__ takes effect.</li><li>__ApplyAndAutoCorrect__: DSC applies any new configurations. After initial application of a new configuration, if the target node drifts from the desired state, DSC reports the discrepancy in logs, and then re-applies the current configuration.</li></ul>|
| ConfigurationMode| string | Specifies how the LCM actually applies the configuration to the target nodes. Possible values are __"ApplyOnly"__,__"ApplyAndMonitor"__, and __"ApplyAndAutoCorrect"__. <ul><li>__ApplyOnly__: DSC applies the configuration and does nothing further unless a new configuration is pushed to the target node or when a new configuration is pulled from a service. After initial application of a new configuration, DSC does not check for drift from a previously configured state. Note that DSC will attempt to apply the configuration until it is successful before __ApplyOnly__ takes effect. </li><li> __ApplyAndMonitor__: This is the default value. The LCM applies any new configurations. After initial application of a new configuration, if the target node drifts from the desired state, DSC reports the discrepancy in logs. Note that DSC will attempt to apply the configuration until it is successful before __ApplyAndMonitor__ takes effect.</li><li>__ApplyAndAutoCorrect__: DSC applies any new configurations. After initial application of a new configuration, if the target node drifts from the desired state, DSC reports the discrepancy in logs, and then re-applies the current configuration.</li></ul>|
| ConfigurationModeFrequencyMins| UInt32| How often, in minutes, the current configuration is checked and applied. This property is ignored if the ConfigurationMode property is set to ApplyOnly. The default value is 15.|
| DebugMode| string| Possible values are __None__, __ForceModuleImport__, and __All__. <ul><li>Set to __None__ to use cached resources. This is the default and should be used in production scenarios.</li><li>Setting to __ForceModuleImport__, causes the LCM to reload any DSC resource modules, even if they have been previously loaded and cached. This impacts the performance of DSC operations as each module is reloaded on use. Typically you would use this value while debugging a resource</li><li>In this release, __All__ is same as __ForceModuleImport__</li></ul> |
| RebootNodeIfNeeded| bool| Set this to __$true__ to automatically reboot the node after a configuration that requires reboot is applied. Otherwise, you will have to manually reboot the node for any configuration that requires it. The default value is __$false__. To use this setting when a reboot condition is enacted by something other than DSC (such as Windows Installer), combine this setting with the [xPendingReboot](https://github.com/powershell/xpendingreboot) module.|
Expand Down
1 change: 1 addition & 0 deletions gallery/TOC.md
Original file line number Diff line number Diff line change
Expand Up @@ -11,6 +11,7 @@
### [Creating a PowerShellGallery Account](psgallery/psgallery_creating_an_account.md)
### [Creating and publishing items](psgallery/Creating-and-Publishing-an-item.md)
### [Publishing guidelines and best practices](psgallery/psgallery-PublishingGuidelines.md)
### [Item manifest and Gallery UI](psgallery/psgallery_ItemManifestAffectingUI.md)
### [Unlisting items](psgallery/psgallery_unlist_items.md)
### [Deleting items](psgallery/Deleting-Items.md)
### [Managing item owners](psgallery/Managing-Item-Owners.md)
Expand Down
139 changes: 139 additions & 0 deletions gallery/psgallery/psgallery_ItemManifestAffectingUI.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,139 @@
# Item manifest values that impact the PowerShell Gallery UI

This topic provides publishers with summary information on how to modify the manifest for their PowerShell Gallery publications so that features of PowerShellGet cmdlets and the PowerShell Gallery UI will be affected.
This content is organized by where the change will appear, starting with the center section, then the navigation area on the left. There is a detail section covering tags, which identifies important tags, as well as some of the more commonly used tags.
There are two topics that provide manifest examples:

* For modules, see [Update Module Manifest](https://docs.microsoft.com/en-us/powershell/gallery/psget/module/psget_update-modulemanifest)
* For scripts, see [Create Script File with Metadata](https://docs.microsoft.com/en-us/powershell/gallery/psget/script/psget_new-scriptfileinfo)

## PowerShell Gallery Feature Elements Controlled by the Manifest

The table below shows the elements of the PowerShell Gallery item page UI that are controlled by the publisher.
Each item indicates if it may be controlled by the module or script manifest.

| UI Element | Description | Module | Script |
| --- | --- | --- | --- |
| **Title** | This is the name of the item that is published to the Gallery | No | No |
| **Version** | The version displayed is the version string in the metadata, and a prerelease if is specified. The primary portion of the version in a Module manifest is the ModuleVersion. For a script, it is identified as .VERSION. If a prerelease version string is specified, it will be appended to the ModuleVersion for modules, or specified as part of .VERSION for scripts. There is documentation for specifying prerelease strings in [modules](https://docs.microsoft.com/en-us/powershell/gallery/psget/module/prereleasemodule), and in [scripts](https://docs.microsoft.com/en-us/powershell/gallery/psget/script/prereleasescript) | Yes | Yes |
| **Description** | This is the Description in the module manifest, and in a script file manifest it is .DESCRIPTION | Yes | Yes |
| **Require license acceptance** | A module can require that the user accept a license, by modifying the module manifest with RequireLicenseAcceptance = $true, supplying a LicenseURI, and providing a license.txt file in the root of the module folder. Additional information is available in the [Require License Acceptance](https://docs.microsoft.com/en-us/powershell/gallery/psgallery/psgallery_requires_license_acceptance) topic. | Yes | No |
| **Release notes** | For modules, this information is drawn from the ReleaseNotes section, under PSData\PrivateData. In script manifests, it is the .RELEASENOTES element. | Yes | Yes |
| **Owners** | Owners are the list of users in the PowerShell Gallery who can update an item. The owner list is not included in the item manifest. Additional documentation describes how to [manage item owners](https://docs.microsoft.com/en-us/powershell/gallery/psgallery/managing-item-owners). | No | No |
| **Author** | This is included in the module manifest as the Author, and in a script manifest as .AUTHOR. The Author field is often used to specify a company or organization associated with an item. | Yes | Yes |
| **Copyright** | This is the Copyright field in the module manifest, and .COPYRIGHT in a script manifest. | Yes | Yes |
| **FileList** | The file list is drawn from the package when it is published to the PowerShell Gallery. It is not controllable by the manifest information. Note: there is an additional .nuspec file listed with each item in the PowerShell Gallery that is not present after installing the item on a system. This is the Nuget package manifest for the item, and may be ignored. | No | No |
| **Tags** | For modules, Tags are included under PSData\PrivateData. For scripts, the section is labelled .TAGS. Note that tags cannot contain spaces, even when they are in quotes. Tags have additional requirements and meanings, which are described later in this topic in the Tag Details section. | Yes | Yes |
| **Cmdlets** | This is provided in the module manifest using CmdletsToExport. Note that the best practice is to explicitly list the items, rather than using the wildcard “*”, as that will improve the load-module performance for users. | Yes | No |
| **Functions** | This is provided in the module manifest using FunctionsToExport. Note that the best practice is to explicitly list the items, rather than using the wildcard “*”, as that will improve the load-module performance for users. | Yes | No |
| **DSC Resources** | For modules that will be used on PowerShell version 5.0 and above, this is provided in the manifest using DscResourcesToExport. If the module is to be used in PowerShell 4, the DSCResourcesToExport should not be used as it is not a supported manifest key. (DSC was not available prior to PowerShell 4.) | Yes | No |
| **Workflows** | Workflows are published to the PowerShell Gallery as scripts, and identified as workflows (see [Connect-AzureVM](https://www.powershellgallery.com/packages/Connect-AzureVM/1.0/Content/Connect-AzureVM.ps1) for an example) in the code. This is not controlled by the manifest. | No | No |
| **Role capabilities** | This will be listed when the module published to the PowerShell Gallery contains one or more role capability (.psrc) files, which are used by JEA. See the JEA documentation for more details on [role capabilities](https://docs.microsoft.com/en-us/powershell/jea/role-capabilities). | Yes | No |
| **PowerShell Editions** | This is specified in a script or module manifest. For modules designed to be used with PowerShell 5.0 and below, this is controlled using Tags. For Desktop, use the tag PSEdition_Desktop, and for core, use the tag PSEdition_Core. For modules that will be used only on PowerShell 5.1 and above, there is a CompatiblePSEditions key in the main manifest. For additional detail, review the PS Edition feature in [the PowerShell Get documentation](https://docs.microsoft.com/en-us/powershell/gallery/psget/module/modulewithpseditionsupport). | Yes | Yes |
| **Dependencies** | Dependencies are the modules in the PowerShell Gallery that are declared in either the module as RequiredModules, or in the script manifest as #Requires –Module (name). | Yes | Yes |
| **Minimum Powershell version** | This can be specified in a module manifest as PowerShellVersion | Yes | No |
| **Version History** | The version history reflects the updates made to a module in the PowerShell Gallery. If a version of an item is hidden using the Delete feature, it will not be displayed in the version history, except to the item owners. | No | No |
| **Project Site** | The project site is provided for modules in the Privatedata\PSData section of the module manifest by specifying a ProjectURI. In the script manifest, it is controlled by specifying .PROJECTURI. | Yes | Yes |
| **License** | A license link is provided for modules in the Privatedata\PSData section of the module manifest by specifying a LicenseURI. In the script manifest, it is controlled by specifying .LICENSEURI. It is important to note that if a license is not provided via the LicenseURI, or within a module, then the terms of use for the PowerShell Gallery specify the terms of use for the item. See the terms of use for details. | Yes | Yes |

## Editing item details

The PowerShell Gallery Edit item page allows publishers to change several of the fields displayed for an item, specifically:

* Title
* Description
* Summary
* Icon URL
* Project home page URL
* Authors
* Copyright
* Tags
* Release notes
* Require license

This approach is not generally recommended, except when needed to correct what is displayed for an older version of a module.
Users who acquire the module will see the metadata does not match what is displayed in the PowerShell Gallery, which raises concerns about the item.
This will frequently result in inquiries going to to the item owners to confirm the change.
It is strongly recommended that any time this approach is used, a new version of the item should be published with the same changes.

## Tag Details

Tags are simple strings consumers use to find items.
Tags are most valuable when they are used consistently across many items related to the same topic. Using multiple flavors of the same word (for example database and databases, or test and testing) typically provides little benefit.
Tags are single-word case-insensitive strings and cannot include blanks. If there is a phrase you believe users will search for, add that to the item description and it will be found in the search results. Use Pascal casing, hyphen, underscore, or period if you are trying to improve readability. Be cautious about creating long, complex, and unusual tags, as they are often misspelled.

There are tags that are important to note, as the PowerShell Gallery and PowerShellGet cmdlets treat them uniquely. PSEdition_Desktop and PSEdition_Core are the specific examples, and are described above.

As noted above, tags provide the most value when they are specific, and used consistently across many items.
As a publisher trying to locate the best tags to use, the easiest approach is to search the PowerShell Gallery for tags you are considering.
Ideally, there will be many items returned, and the item descriptions will align with your use of that key word.

For reference, here are some most commonly used tags as of 12/14/2017.
In some cases, there are similar but perhaps less ideal options listed beside the tag.
It is a best practice to use the Preferred Tag, as that will result in less noise, and better search results for consumers.


| **Preferred tag** | **Alternatives and notes** |
| --- | --- |
| **Azure** | |
| **DSC** | DesiredStateConfiguration is less desirable, it’s too long |
| **ResourceManager** | ARM is used to describe group of processors, and should not be used for Azure Resource Manager | **DSCResourceKit** | |
| **SQL** | |
| **AWS** | |
| **DSCResource** | |
| **Automation** | |
| **REST** | |
| **ActiveDirectory** | AD is not currently used by itself |
| **SQLServer** | |
| **DBA** | |
| **Security** | Defense is less precise |
| **Database** | Databases (plural) is less desirable |
| **DevOps** | |
| **Windows** | |
| **Build** | |
| **Deployment** | Deploy is used somewhat less often |
| **Cloud** | |
| **GIT** | |
| **Test** | Testing is less desirable |
| **VersionControl** | Version is less precise, although used more frequently |
| **Logging** | Preferred use of logging as an action |
| **Log** | Preferred use of Log as a thing |
| **Backup** | |
| **IaaS** | |
| **Linux** | |
| **IIS** | |
| **AzureAutomation** | |
| **Storage** | |
| **GitHub** | |
| **Json** | |
| **Exchange** | |
| **Network** | Networking is similar, less often used |
| **SharePoint** | |
| **Reporting** | Reporting is an action, report is a thing |
| **Report** | Report is a thing |
| **WinRM** | |
| **Monitoring** | |
| **VSTS** | |
| **Excel** | |
| **Google** | |
| **Color** | |
| **DNS** | |
| **Office365** | Spelling out Office is preferable. O365 is less commonly used, although shorter | **Gitlab** | |
| **Pester** | |
| **AzureAD** | |
| **HTML** | |
| **Hyper-V** | HyperV is less common as a tag |
| **Configuration** | |
| **ChatOps** | |
| **PackageManagement** | |
| **WMI** | |
| **Firewall** | |
| **Docker** | |
| **Appveyor** | |
| **AzureRm** | Used primarily for the AzureRM modules |
| **Zip** | |
| **MSI** | |
| **Mac** | |
| **PoshBot** | |


Original file line number Diff line number Diff line change
Expand Up @@ -441,7 +441,7 @@ This method works only for classes that have a null constructor, that is, a
constructor that has no parameters. The object properties must be public and
settable.

For more information, see [about_Object_Creation(about_Object_Creation.md)].
For more information, see [about_Object_Creation](about_Object_Creation.md).

### ConvertFrom-StringData

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,6 @@ functions, cmdlets, or snap-ins.
#Requires -PSSnapin <PSSnapin-Name> [-Version <N>[.<n>]]
#Requires -Modules { <Module-Name> | <Hashtable> }
#Requires -ShellId <ShellId>
#Requires -RunAsAdministrator
```

### RULES FOR USE
Expand All @@ -40,7 +39,7 @@ functions, cmdlets, or snap-ins.

### PARAMETERS

-Version <N>[.<n>]
-Version \<N\>[.\<n\>]

Specifies the minimum version of Windows PowerShell that the script requires.
Enter a major version number and optional minor version number.
Expand All @@ -51,7 +50,7 @@ For example:
#Requires -Version 3.0
```

-PSSnapin <PSSnapin-Name> [-Version <N>[.<n>]]
-PSSnapin \<PSSnapin-Name\> [-Version \<N\>[.\<n\>]]

Specifies a Windows PowerShell snap-in that the script requires. Enter the
snap-in name and an optional version number.
Expand All @@ -62,7 +61,7 @@ For example:
#Requires -PSSnapin DiskSnapin -Version 1.2
```

-Modules <Module-Name> &#124; <Hashtable>
-Modules \<Module-Name\> &#124; \<Hashtable\>

Specifies Windows PowerShell modules that the script requires. Enter the
module name and an optional version number. The Modules parameter is
Expand Down
Loading

0 comments on commit 18e3bfa

Please sign in to comment.