#requires your scripts

Anith » #requires your scripts

Anith » #requires your scripts — Sat, 07 Feb 2009 00:51:42 GMT

PingBack from http://www.anith.com/?p=6484

re: #requires your scripts

Stranger — Sat, 07 Feb 2009 09:23:25 GMT

Why not changing the file extension from ps1 to ps2? Seems more obvious to me...

Or do we have ps2 in PowerShell 3 to complete the Microsoft version numbering chaos?

re: #requires your scripts

Mike — Sun, 08 Feb 2009 01:50:45 GMT

Of course, the easiest way to prevent someone from running a version 2 script on a version 1 shell would have been to enforce renaming the 'required' file extension from .ps1 to .ps2 -- the extension's original intent.

#requires your scripts

CK — Sun, 08 Feb 2009 09:54:07 GMT

Renaming the extension would be the best way to go, however, then we would need updated VIM plugins. That's ok though as the syntax plugin needs some minor parameter refactoring anyway;-)

re: #requires your scripts

James — Sun, 08 Feb 2009 21:54:30 GMT

Compatibility is important.

But I think this time Microsoft outperformed themselves.

So much that version 2 is installed in C:\Windows\system32\WindowsPowerShell\v1.0\

(On 32bit Vista, at least).

re: #requires your scripts

Merddyn — Mon, 09 Feb 2009 00:28:23 GMT

Unfortunately, I found out the hard way it is possible to write a script using V2 features and not even realize it.

For example, binding a new object to System.DirectoryServices.DirectoryEntry in v2 allows me to take advantage of the inherited 'children' method to enumerate the targeted object, however in v1 that isn't available to me because it appears to expect an overload. Not sure why this behavior would be different since this is the .Net namespace and not a PowerShell command, but it is. For some reason I thought it should work the same.

re: #requires your scripts

Bob Landau — Tue, 10 Feb 2009 06:50:01 GMT

Renaming the extension is not enough. There will be differences between Win7 and WS2008R2 vs Vista/XP even if they are using v2 of PS.

http://blogs.msdn.com/powershell/archive/2008/10/29/574-reasons-why-we-are-so-proud-and-optimistic-about-w7-and-ws08r2.aspx

I am hoping that when this RTM's or prior at least the helpfiles for the cmdlets will designate whether they are for v1 or 2 and which OS.