Windows PowerShell, Invalid Certificates, and Automated Downloading

re: Windows PowerShell, Invalid Certificates, and Automated Downloading

ScriptingGuy1 — Fri, 03 Sep 2010 15:55:25 GMT

@Scott Thanks :-)

@Doug You are correct that if you remove the Function part, and simply use the code from the function directly, it will work the same. It is not a 1.0 or a 2.0 thing. In PowerShell 2.0 additional features were added to functions to make them work more like cmdlets. In PowerShell 1.0 functions were like VBScript Subroutines and Functions. The advantage of a function is that it can encapsulate logic and make the script easier to read. It can also allow for easy code reuse. If a function is stored in a file it can be dotsourced into script, and you do not need to copy the code into the script. But if you have additional code, it will execute. I have several articles on functions. Use the getting started / functions tags.

re: Windows PowerShell, Invalid Certificates, and Automated Downloading

Doug — Wed, 28 Jul 2010 18:42:51 GMT

I'm not understanding the advantage of the function inside the script... You say "The advantage of this is that it allows you to run the script without needing to dot-source a function into your Windows PowerShell console, or copy a function into your profile." If I just put the contents of the function in a script, it works just fine in PowerShell 2.0 - is this a 1.0 thing I'm missing?

Thanks in advance for the clarification.

-Doug

re: Windows PowerShell, Invalid Certificates, and Automated Downloading

Scott Muc — Tue, 27 Jul 2010 16:31:42 GMT

Thanks you for this article! We've been struggling with this problem and we're using this function to replace a very convoluted script we've made. I really like the simplicity of this implementation.