Bonjour/Hello

J'aimerais vous mentionner que mon anglais n'est pas très bon. Par contre, comme je suis un programmeur depuis 20 ans, je suis en mesure de lire l'anglais et d'écrire des FOR, THIS, IF, NEXT..., mais je suis moins bon en écriture de texte. Alors je vous prie de m'excuser si certaines phrases sont mal écrites. Je vais laisser la version en français (Au besoin).

<-- I would like to tell you that my English is not very good. On the other hand, since I have been a programmer for 20 years, I am able to read English and write FOR, THIS, IF, NEXT ..., but I am less good at writing text. So I apologize if some sentences are poorly written. I will leave the French version (As needed). -->

Depuis que je programme en PowerShell, j'ai toujours eu un problème avec la partie d'aide d'un programme en PowerShell et je vais vous l'expliquer.

Dans mon entreprise, nous avons décidé de programmer plusieurs fonctions portables qui ont un usage unique. À titre d'exemple, une fonction qui va juste extraire les données d'un fichier de type CSV ou une fonction qui va faire une requête SQL, par la suite les programmes vont retourner le résultat au programme parent. La fonction sera utilisé par des programmes parents d'automatisation des système. Le programme ConsoleServices.ps1 contient une section qui peut faire l'appel de l'une de ses fonctions, si l'événement est déclenché par l'utilisateur. Cette façon de procédé permet de ne pas refaire la même programmation à plusieurs reprises. Je crois que beaucoup d'entreprises fonctionnent comme nous.

Alors, quand je fais un programme, j'aimerais vraiment pouvoir donner dans l'aide les prérequis dont la fonction aura besoin pour exécuter sa tâche jusqu'à la fin. Donc, il serait utile d'ajouter le mot clé ".PREREQUISITE" selon moi.

Ça ne changera pas le monde, mais ça va l'améliorer!

English version --------------------------

Since programming in PowerShell, I've always had a problem with the help part of a program in PowerShell and I'll explain it to you.

In my company, we have decided to program several portable functions which have a single use. For example, a function which will just extract data from a CSV type file or a function which will make an SQL query, subsequently the programs will return the result to the parent program. The function will be used by parent system automation programs. The ConsoleServices.ps1 program contains a section that can make a call to one of its functions, if the event is triggered by the user. This way of proceeding makes it possible not to repeat the same programming several times. I believe a lot of businesses operate like us.

So when I make a program, I would really like to be able to give in the help the prerequisites that the function will need to perform its task until the end. So, it would be useful to add the keyword ".PREREQUISITE" according to me.

It won't change the world, but it will improve it!

Exemple/Example :

Function VerbMaFonction
{
<#
.SYNOPSIS
Returns a list of services that are set to start automatically, are not
currently running, excluding the services that are set to delayed start.

.DESCRIPTION

Get-MrAutoStoppedService is a function that returns a list of services from

the specified remote computer(s) that are set to start automatically, are not

currently running, and it excludes the services that are set to start automatically

with a delayed startup.

.PARAMETER ComputerName

The remote computer(s) to check the status of the services on.

.PARAMETER Credential

Specifies a user account that has permission to perform this action. The default

is the current user.

.EXAMPLE

 Get-MrAutoStoppedService -ComputerName 'Server1', 'Server2'

.INPUTS

String

.OUTPUTS

PSCustomObject

.PREREQUISITE

-Put the prerequisites for this function here.

-Mettre les conditions préalables à cette fonction.

Example : Verb_MyFunction_Requis or Beginning in PowerShell 3.0

.NOTES

Author:  Mike F Robbins

Website: <a rel="nofollow noreferrer" href="http://mikefrobbins.com">http://mikefrobbins.com</a>

Twitter: @mikefrobbins

>

}

Martin Benoit-Goyette

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 208e74df-f0c4-2841-82f9-8c9ff22e8b31
Version Independent ID: 3ae6b0ce-e9bb-a441-92b2-cf12402e1f97
Content: aboutCommentBasedHelp - PowerShell
Content Source: reference/7.1/Microsoft.PowerShell.Core/About/aboutCommentBasedHelp.md
Product: powershell
Technology: powershell-conceptual
GitHub Login: @SteveL-MSFT

Scenario:
We are filtering traces captured in *.etl files using the following Cmdlets: New-PefTraceSession, Add-PefMessageSource, and Start-PefTraceSession. After the filter we expect the filtered file to be saved as a .matu file. The traces themselves are captured using netevents sessions, logman and xperf. Most of these works fine but occassionally we run into the below error which causes that particular .etl trace file to not be analyzed/filtered.

-----Exception-----System.ArgumentException: An item with the same key has already been added.
at System.ThrowHelper.ThrowArgumentException(ExceptionResource resource)
at System.Collections.Generic.Dictionary2.Insert(TKey key, TValue value, Boolean add)
at Microsoft.ProtocolTools.Runtime.Persistence.Project.AddMetadataSection(Nullable1 id, String name, String type, String description, String path)
at Microsoft.Opn.Runtime.Messaging.MessageStoreBase.CopyMessageMetadataItem(String name, String type, String dataType, MetadataItem item)
at Microsoft.Opn.Runtime.Monitoring.MetadataManager.NewMessageMetadataEventHandler(Object sender, NewMessageMetadataEventArgs e)
at Microsoft.Opn.Runtime.Monitoring.MetadataManager.Initialize(IMessageStore messageStore)
at Microsoft.Opn.Runtime.Monitoring.CaptureJournal.set_messageStore(IMessageStore value)
at Microsoft.Opn.Runtime.Monitoring.CaptureJournal.Start(Boolean clearExistingMessages)
at Microsoft.Protocols.Tools.PowerShell.Actions.StartTraceSessionAction.<ExecuteImpl>b__0()
at Microsoft.Protocols.Tools.PowerShell.CaptureEngine.Post(Action action, Boolean startPump)
at Microsoft.Protocols.Tools.PowerShell.Actions.Action.Execute()
-----FullyQualifiedErrorId-----StartTraceSession,Microsoft.Protocols.Tools.PowerShell.Actions.StartPefTraceSessionCmdlet

We are not sure what key is duplicated here but that we skip filtering the entire file (which can be upto 1.2 GB in size) because of the above error is undesirable. We would like to see the associated .matu file when we use -SaveOnStop switch. Pointing me to someone who can help would be of great assistance as well. Attaching a sample of our filter commands.

Most Important aspects after any corruption in Exchange server that how to get EDB files back in appropriate manner because it is very difficult task for every Exchange users when he doesn't have any depth knowledge about Exchange inbuilt utilities. So only for purpose GSTECH company came with excellent tool "Exchange EDB file Recovery Tool" that only made to assist Exchange users to come out from Exchange server issues problem. This fabulous and outstanding EDB to PST Recovery remarkably work on every supportive edb file upto 2019 to make it readable and usable into various platforms like- PST, EML, MSG , HTML and Office 365 directly too.

Just download EDB to PST Freeware software and check is working strength without paying any cost. It shows you how software repair EDB file and Export Exchange mailboxes into required destinations with respective mails attachments.

Read more about this topic from here- https://www.gstechsoftware.com/exchange-edb-recovery-software.html

Most Important aspects after any corruption in Exchange server that how to get EDB files back in appropriate manner because it is very difficult task for every Exchange users when he doesn't have any depth knowledge about Exchange inbuilt utilities. So only for purpose GSTECH company came with excellent tool "Exchange EDB file Recovery Tool" that only made to assist Exchange users to come out from Exchange server issues problem. This fabulous and outstanding EDB to PST Recovery remarkably work on every supportive edb file upto 2019 to make it readable and usable into various platforms like- PST, EML, MSG , HTML and Office 365 directly too.

Just download EDB to PST Freeware software and check is working strength without paying any cost. It shows you how software repair EDB file and Export Exchange mailboxes into required destinations with respective mails attachments.

Read more about this topic from here- https://www.gstechsoftware.com/exchange-edb-recovery-software.html

Most Important aspects after any corruption in Exchange server that how to get EDB files back in appropriate manner because it is very difficult task for every Exchange users when he doesn't have any depth knowledge about Exchange inbuilt utilities. So only for purpose GSTECH company came with excellent tool "Exchange EDB file Recovery Tool" that only made to assist Exchange users to come out from Exchange server issues problem. This fabulous and outstanding EDB to PST Recovery remarkably work on every supportive edb file upto 2019 to make it readable and usable into various platforms like- PST, EML, MSG , HTML and Office 365 directly too.

Just download EDB to PST Freeware software and check is working strength without paying any cost. It shows you how software repair EDB file and Export Exchange mailboxes into required destinations with respective mails attachments.

Use the best and reliable software is eSoftTools OST to PST Converter software that supports to work and convert all Outlook OST file items such as emails, contacts, calendar, notes, user-created folders, all inbox, and attachments. The software converts single and multiple files with original formats. It shows the free preview before conversion. The software recovers all corrupted items of Outlook OST file and Converter the Outlook OST file into various file types in MSG, MBOX, EML, PST, vCard, vCal, and Office 365, etc. The software saved OST contacts in vCard format and OST calendar meetings in vCal format.

To Know More:- https://www.esofttools.com/convert-ost-to-pst.html

Try "eSoftTools OST to PST Converter software" which can easily recover lost database from your corrupt OST files like- emails, dates, calendars, tasks, notes, inbox items, journals, and appointments and offers to convert OST to PST. This Exchange OST recovery software also can convert the Outlook OST file to PST, MSG, EML, EMLX, vCard, MBOX, Gmail, YahooMail, Zimbra, office 365, etc. It also comes with a comes split feature to reduce the file size of resulted in PST. Get a free demo version of this software that is able to give you an instant preview of your damaged OST file inner items and allow you to save its 25 items from each folder to PST free of cost.

To Know More:- https://www.esofttools.com/ost/

Windows Server 2019 and Powershell 5.1 have broken the -ExternalIPInterfaceAddressPrefix parameter in the New-NetNat cmdlet. In 2012 R2, you specify the external networks on your server using this parameter and specifying the Network and CIDR mask (10.95.1.0/24). In 2019 and Powershell 5.1, this parameter is broken and you receive an error saying "The parameter is incorrect" invariably. The only way to create a NAT configuration in 2019 is to use the new InternalIPInterfaceAddressPrefix parameter, but this seems to prevent you from creating new External Addresses. Whenever I create a NAT in Server 2019 using the InternalIPInterfaceAddressPrefix parameter, I am unable to add an External Address and I get an "element not found" error. This functionality worked in 2012 R2, but is broken in 2019.