Skip to content

Commit 99473b6

Browse files
committed
RFC for PowerShell Core Interop Module
1 parent bcbec8d commit 99473b6

File tree

1 file changed

+4
-3
lines changed

1 file changed

+4
-3
lines changed

1-Draft/RFCXXXX-PowerShell-Core-Interop-Module.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ Area: Standard Modules
1414
Comments Due: 5/1/2017
1515
---
1616

17-
# Interop Module Which Emulates Windows On PowerShell Core On Non-Windows
17+
# Interop Module Which Patches PowerShell Core Environment to Match The "Developed On" Platform of the Code
1818

1919
I have written one script for configuring security for AWS which runs, without modification, on Linux or Windows.
2020

@@ -49,9 +49,10 @@ to "windowize" the Linux platform and would be confusing for Linux professionals
4949
- Standard shipped-with PowerShell Core module
5050
- Written as a script
5151
- That "fixes up" a target environment (Windows or PowerShell)
52-
- with common standard pointers
52+
- with common standard pointers for the "Developed on" platform
5353
- or code samples for common things that need to be done from the "developed on" platform
54-
- including code samples of methods that simply work on both platforms unchanged
54+
- using existing reference technology common to both platforms and available in PowerShell (e.g. Environment Variables & PowerShell Variables)
55+
- and includes code samples of methods that simply work on both platforms unchanged (e.g. A way to check bitness that works unmodified on both platforms - even though there is not a PowerShell standard for exposing this information)
5556
- that requires some action from an administrator to enable (e.g. run a CMDLet in their script or a machine based profile)
5657

5758
###Example

0 commit comments

Comments
 (0)