Comments for Use PowerShell

Comment on Starting 2012 with a Bang by Episode 171 – Listener Call-In « PowerScripting Podcast

Episode 171 – Listener Call-In « PowerScripting Podcast — Tue, 10 Jan 2012 04:24:21 +0000

[...] Steven Murawski! [...]

Comment on When Import-Module Does Not by Poshoholic

Poshoholic — Fri, 06 Jan 2012 17:37:54 +0000

Hey Steve, I thought of another good test to try out with this, but too busy right now to test it. If module auto-load is enabled, and if modules auto-load when you use aliases, then I suspect if you configure PowerShell this way that you would be able to auto-load a module using an alias only to then get a command not found error. I suppose this makes sense, because the command indeed would not be found, but it’s an interesting use case because you end up changing the system state (loading a module) with an invalid command (according to how you configured modules to load: without aliases). The default parameter values feature will probably reveal a bunch of unusual scenarios like this.

Comment on PowerShell V3 – Auto-loading of Modules by Joel 'Jaykul' Bennett

Joel 'Jaykul' Bennett — Fri, 06 Jan 2012 17:27:21 +0000

Well, in your host $Env:PSModulePath is the environment variable… and IF you have it set, whatever you see (or set) there should be what’s being used.

But yes, that’s what I was getting at: you can set both the PSModulePath and PSDiableModuleAutoLoading in your profile but there, they only affects you when your profile is run (ie: not remote sessions). However, if you set them in the “System Properties” control panel in the “Environment Variables” dialog, then it’s basically permanent… and affects either your user or your machine, depending on where you set it.

Personally, I’d encourage people to set their PSModulePath — the default path seems to have changed in PS3 from PS2, but in any case (as a developer, not a sysadmin), I actually like the autoloading

Comment on PowerShell V3 – Default Parameter Values by When Import-Module Does Not « Use PowerShell

When Import-Module Does Not « Use PowerShell — Fri, 06 Jan 2012 16:47:04 +0000

[...] « PowerShell V3 – Auto-loading of Modules PowerShell V3 – Default Parameter Values [...]

Comment on PowerShell V3 – Auto-loading of Modules by Steven Murawski

Steven Murawski — Fri, 06 Jan 2012 16:37:19 +0000

The PSModulePath is built by taking the user environmental variable and appending the machine environmental variable, so values set in the user variable will always (by default) precede the machine level paths.

Yes, you can modify that once the shell is started (or in your profile), but that change is not permanent. If it is in your profile, you have to manage whether you want it for all shells or just specific ones, and whether that should be a machine level profile or specific to you.

I’ll likely turn it off for myself, but it can provide an unexpected behavior if you don’t know how it is finding the module to load.

Comment on PowerShell V3 – Auto-loading of Modules by Joel 'Jaykul' Bennett

Joel 'Jaykul' Bennett — Fri, 06 Jan 2012 16:31:23 +0000

Of course you CAN pick the order of module loading: you control the PSModulePath — it’s an environment variable you can set permanently in Windows or temporarily in your profile script, etc.

You can also turn it off or control it via $Env:PSDisableModuleAutoLoading = “None”

Comment on PowerShell V3 – Auto-loading of Modules by When Import-Module Does Not « Use PowerShell

When Import-Module Does Not « Use PowerShell — Fri, 06 Jan 2012 15:33:58 +0000

[...] « Starting 2012 with a Bang PowerShell V3 – Auto-loading of Modules [...]

Comment on Tip: Passing Parameters by Brian.Christiansen

Brian.Christiansen — Fri, 11 Nov 2011 05:20:47 +0000

Thanks for the tip about “Passing Parameters” One of the points raised in the post was about passing a text datatype parameter to a procedure called in the background and the fact that the contents of the text variable are lost. The same code called in the foreground works at both parameters are being passed as one is that PowerShell does not use the parens “()” to enclose parameters (that is only method calls from objects).Thanks Steven Murawski.

Comment on Waiter, There’s a Bug in My Get-Help! by Alex

Alex — Sun, 06 Nov 2011 16:50:21 +0000

I voted it up. Thanks for fixing the bug. I was about to point it out but Rob beat me to it!

Comment on Exploring the .NET Framework with PowerShell – Static Members (Part 4) by Jean H.

Jean H. — Sun, 16 Oct 2011 13:24:32 +0000

Hi Steve, thank you for sharing this. I really could use more of this information on the .NET Framework. We’ve got a lot of things to cover. Thanks again!

Comment on How To Send E-Mail From PowerShell by Darin

Darin — Wed, 12 Oct 2011 18:58:58 +0000

Flog=Flag

Comment on How To Send E-Mail From PowerShell by Darin

Darin — Wed, 12 Oct 2011 18:58:16 +0000

Is there a way to add a follow-up notification to the send-emailmessage like the header x-Message-Flog “For your information”?

Comment on Using the Sync Framework from PowerShell by Thor

Thor — Sat, 17 Sep 2011 17:47:17 +0000

Nice code. it works perfectly.
Do you know how to sync ntfs permissions as well?

Comment on Adding Configuration To Remoting by Adam W.

Adam W. — Fri, 16 Sep 2011 13:19:27 +0000

At start I thought it is not working, but upon I have reviewed it again I missed one symbol. Thanks for this post

Comment on The Myth of Advanced Functions–CmdletBinding for the Rest of our Scripts by Architect Cape Town

Architect Cape Town — Thu, 01 Sep 2011 06:49:56 +0000

Matt, thanks for the solution. I was getting the same error at the start of my script, but it is all sorted out now thanks to you. I was making the same silly mistake lol. Thanks a lot, both of you.