Major changes are as follows: - Avoid `SecuritySupport.IsProductBinary` and unnecessary AMSI/suspicious code scan at startup time - Update `CompiledScriptBlockData.IsProductCode` to avoid unnecessary calls to `IsProductBinary`, which attempts to retrieve catalog signature of the target file. - Update `PerformSecurityChecks` to skip AMSI and suspicious code scan for the `.psd1` file that contains a safe `HashtableAst` only. - Use customized `ReadOnlyBag` instead of `ImmutableHashSet` so that we can avoid loading the `System.Collections.Immutable.dll` completely. - Replace `SHA1` with `CRC32` when generating module analysis cache file name - This remove the loading of `System.Security.Cryptography.Algorithms.dll` at startup - Move `ConvertFrom-SddlString` to C# to remove the `Utility.psm1` file. - Crossgen `Microsoft.ApplicationInsights.dll` and enable tiered compilation - Even pwsh with crossgen assemblies spends a lot time in jitting at the startup, about `191.6ms` comparing with `24.7ms` for Windows PowerShell. - Jitting `Microsoft.ApplicationInsights.dll` takes about `51.6ms`. - By crossgen `Microsoft.ApplicationInsights.dll` and enable tiered compilation, the jitting time drops to about `98.9ms`. |
||
---|---|---|
.. | ||
AppImageThirdPartyNotices.txt | ||
av_colors_128.svg | ||
Avatar.svg | ||
avatar_128.svg | ||
files.wxs | ||
license.rtf | ||
macDialog.png | ||
patch-template.wxs | ||
Powershell-preview.icns | ||
Powershell.icns | ||
Powershell_64.png | ||
powershell_128.svg | ||
Powershell_256.png | ||
Powershell_av_colors.ico | ||
Powershell_avatar.ico | ||
Powershell_black.ico | ||
Powershell_black_64.png | ||
Product.wxs | ||
ps_black_64.svg | ||
ps_black_128.svg | ||
pwsh.1.ronn | ||
pwsh.manifest | ||
README.md | ||
WixUIBannerBmp.bmp | ||
WixUIDialogBmp.bmp | ||
WixUIInfoIco.bmp |
Use of Trademarked Logos
The assets in this folder are trademarked by Microsoft and don't fall under the same License as the source code.
Permitted Uses
Parties interested in using these logos can review the Use of Microsoft Copyrighted Material page. If the use falls into any of those categories, you can move forward with the use and will not need additional permission.
Third Party Permission Requests
If questions remain after reviewing the permitted uses page, please submit a request to Third Party Permissions. The people supporting this will direct the request depending upon the content.
If a request needs to be submitted to the Third Party Permissions, the request should include the following:
- A statement that the Use of Microsoft Copyrighted Material was reviewed and did not address the situation.
- A statement that Microsoft (and not a third party) is the owner of the logo at issue.
- Clear identification of the materials to be used (i.e., the picture of the book cover included by the author in the letter request should suffice).
- A description, including URLs of how they found or located the logo.
- A description of how the party intends to use or distribute the logo (i.e., that it is for the book cover of an instructional book on PowerShell).
- A description of how long the party needs to use the logo.