Repository navigation
docs: add reference assembly prerequisites for C# cmdlets - #13368
OKAN TIKTAS (OKAN-SOFTWARE) wants to merge 3 commits into
Conversation
PoliCheck Scan ReportThe following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans. ✅ No issues foundMore information about PoliCheckInformation: PoliCheck | Severity Guidance | Term |
There was a problem hiding this comment.
🟢 Approval recommended
No active review issues are recorded for the documentation update explaining PowerShell reference assembly prerequisites.
No open issues 🎉
What changed in this PR
Adds compilation prerequisites to the C# cmdlet tutorial, addressing #4210 by explaining how to obtain the required System.Management.Automation reference assemblies.
Changes:
- Documents reference assembly packages for Windows PowerShell 5.1 and 5.0, including a 5.1
PackageReferenceexample. - Explains compilation-only use and links to guidance for choosing packages for other PowerShell versions.
- Updates the article’s modification date.
| File | Description |
|---|---|
reference/docs-conceptual/developer/cmdlet/how-to-write-a-simple-cmdlet.md |
Adds reference assembly prerequisites and package guidance; updates the modification date. |
Review effort: Balanced
|
Learn Build status updates of commit 970b6a1: 💡 Validation status: suggestions
reference/docs-conceptual/developer/cmdlet/how-to-write-a-simple-cmdlet.md
For more details, please refer to the build report. Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them. |
PoliCheck Scan ReportThe following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans. ✅ No issues foundMore information about PoliCheckInformation: PoliCheck | Severity Guidance | Term |
|
Learn Build status updates of commit 13e0e21: 💡 Validation status: suggestions
reference/docs-conceptual/developer/cmdlet/how-to-write-a-simple-cmdlet.md
For more details, please refer to the build report. Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them. |
|
Learn Build status updates of commit a741db9: ✅ Validation status: passed
For more details, please refer to the build report. |
PoliCheck Scan ReportThe following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans. ✅ No issues foundMore information about PoliCheckInformation: PoliCheck | Severity Guidance | Term |
Summary
System.Management.Automationwhen compiling C# cmdlets.Why
The existing tutorial demonstrates C# code that depends on
System.Management.Automation, but does not explain how to obtain the required reference assemblies.These prerequisites help developers prepare their projects before compiling the example.
Fixes #4210
Validation
git diff --checkpassed.AI assistance
AI assistance was used to draft and review the documentation change.
I, Okan Tiktas, personally reviewed the final changes and take responsibility for this contribution.