Comments for 8net.co.uk

Comment on IPv6 and Win7 by Pritesh

Pritesh — Sun, 07 Aug 2011 12:35:45 +0000

Found the web site where I got the above information: http://itexpertvoice.com/home/troubleshooting-ipv6-on-windows-7-and-why-its-worth-the-bother/

Comment on PowerShell edit function by Pritesh

Pritesh — Wed, 06 Apr 2011 11:57:12 +0000

Thanks Jeff, didn’t know about the psedit function in ISE. I’ve thought long and hard for an argument to support the script: I shaved off two letters in the command? Just kidding. I wanted something that was uniform to both environments, one of the things I would like to add is the ability to create a file if it doesn’t exist – my next action on this script.

(I’m going to need a to-do list just for PowerShell).

Comment on PowerShell edit function by Jeffery Hicks

Jeffery Hicks — Sun, 03 Apr 2011 13:59:31 +0000

To be clear, if you are in the console invoking the PS1 script will probably open Notepad or whatever application you have associated with the extension. In the ISE I also think there is default function called psedit

psedit myfile.ps1

Finally, since you aren’t processing any pipelined objects, you don’t really need the Begin and End script blocks. But overall a good construct.

Comment on VirtualBox and VM cloning by PowerCamp London 19-20Mar11 | 8net.co.uk

PowerCamp London 19-20Mar11 | 8net.co.uk — Sat, 26 Mar 2011 17:21:42 +0000

[...] You can see an example of the PowerShell community at work on my blog – Jeffery Hicks helping me to make better scripts through comments, better post a question on Twitter with #PowerShell in your message. You can also check out a before and after of a function I wrote to see how much PowerShell has helped me: virtualbox and vm cloning. [...]

Comment on VirtualBox and VM cloning by Pritesh

Pritesh — Fri, 25 Mar 2011 13:09:39 +0000

Oh yea!! Bring it on Jeffery!! Thank you for the feed back – there shall be a round three!!

Comment on VirtualBox and VM cloning by Jeffery Hicks

Jeffery Hicks — Thu, 24 Mar 2011 19:41:57 +0000

If you don’t mind a little more constructive feedback, which I think will help with future scripts and functions. First, I always recommend casting your parameter variables to the proper type.

[string]$base

Since you aren’t pipelining anything into the function the Begin/Process/End scriptblocks are irrelevant. I think you can just enter your code.

Take a look at Join-Path for constructing paths. I think it is a little easier to use and makes you less prone to concatenation errors.

What happens if the CreateVM expression fails? Or any of the other Invoke-Expression commands?

Since you are using cmdletbinding, why not add some Write-Verbose lines so the user can track what is happening or troubleshoot? All of your comments could easily become Write-Verbose lines. I also use Write-Verbose to show values of variables and parameters.

Finally, when you are ready to really go to the next level, you can add SupportsShouldProcess to the function (-WhatIf). But that’s the cherry on top of the icing on the cake.

Keep up the good work.

Comment on VirtualBox and VM cloning by Pritesh

Pritesh — Thu, 24 Mar 2011 18:31:59 +0000

Yup, removed the line altogether.

Comment on VirtualBox and VM cloning by Pritesh

Pritesh — Thu, 24 Mar 2011 18:30:53 +0000

Thanks for the feed back 0.02, now named Copy-VM to fit with the verb-noun structure has this .

Comment on VirtualBox and VM cloning by Microsoft Points Generator

Microsoft Points Generator — Sun, 20 Mar 2011 18:17:48 +0000

Daily Recommendations…

Here are some useful websites that I have found today while browsing the internet. These sites can be found below….

Comment on VirtualBox and VM cloning by Jeffery Hicks

Jeffery Hicks — Fri, 18 Mar 2011 18:11:57 +0000

Is the last line just to clear out variables? If so you shouldn’t really need to since they only exist in the script scope. But if you really want to remove them, then use Remove-Variable.

remove-variable a,b,c,d

Just specify the variable name, don’t include the $.