SlickEdit Community

Archived Read Only Forums => SlickEdit 2016 v21 Beta Discussion => Topic started by: jporkkahtc on September 26, 2016, 06:53:13 pm

Title: Powershell extensions
Post by: jporkkahtc on September 26, 2016, 06:53:13 pm
Powershell using PS1 and PSM1, but slick only knows PS1 by default.
It oughta include PSM1.

Title: Re: Powershell extensions
Post by: Clark on September 26, 2016, 09:21:23 pm
Added for RC 4
Title: Re: Powershell extensions
Post by: jporkkahtc on September 26, 2016, 09:41:02 pm
There are a number of other extensions for Powershell, but I don't know if those apply for scripts or other types of data.


PS1 seems an odd choice.
Is there a PS2? PS3?



Title: Re: Powershell extensions
Post by: Clark on September 26, 2016, 09:52:53 pm
I didn't see any others
Title: Re: Powershell extensions
Post by: jporkkahtc on September 26, 2016, 10:02:10 pm
C:\>assoc | findstr -i powershel
.ps1=Microsoft.PowerShellScript.1
.ps1xml=Microsoft.PowerShellXMLData.1
.psc1=Microsoft.PowerShellConsole.1
.psd1=Microsoft.PowerShellData.1
.psm1=Microsoft.PowerShellModule.1


https://msdn.microsoft.com/en-us/library/dd878324%28v=vs.85%29.aspx?f=255&MSPPError=-2147217396

https://x64.us/windows-powershell-filename-extensions
Title: Re: Powershell extensions
Post by: Clark on September 26, 2016, 11:09:54 pm
I didn't think the .ps1xml, .psc1, or .psd1 files actually contain power shell source code.

.ps1xml is XML " The Types.ps1xml file in the Windows PowerShell installation directory ($pshome) is an XML-based text file..."

The sample .psc1 files look like XML.

.psd1 could be powershell code but the Wikipedia page says its a powershell data file. Sure doesn't sound like powershell code to me.