Thanks,
jeff
$(pwd).path
-a
$myinvocation.mycommand.path
see
http://msgoodies.blogspot.com/2007/04/powershell-writing-debug-output.html
for more information
--
Richard Siddaway
Please note that all scripts are supplied "as is" and with no warranty
Blog: http://richardsiddaway.spaces.live.com/
PowerShell User Group: http://www.get-psuguk.org.uk
Using: $myinvocation.mycommand.path (as Rich Suggest) is much better IMO.
"Alex Harden" <aha...@gmail.com> wrote in message
news:1180719264.3...@q66g2000hsg.googlegroups.com...
split-path $myinvocation.scriptname
~Clint
"Alex Harden" <aha...@gmail.com> wrote in message news:1180719264.3...@q66g2000hsg.googlegroups.com...
AppDir:C:\Documents and Settings\Administrator\Application Data\Microsoft
Corporation\Microsoftr Windowsr Operating System\6.0.5430.0
I realize this is because it is probably using the Powershell.exe info as it
is the exe. However, it would seem like this should be fixed somehow to
allow cmdlets to use this info consistent with other applications.
--
William Stacey [C# MVP]
PowerLocker, PowerPad
www.powerlocker.com
"Jeff Jarrell" <jjarr...@yahoo.com> wrote in message
news:%23g%23IzBGp...@TK2MSFTNGP03.phx.gbl...
"RichS" <Ri...@discussions.microsoft.com> wrote in message
news:2170ECCA-1467-48BC...@microsoft.com...