Skip to main content

Organizing your PowerShell Workspace

By

If you are like me, you have multiple monitors stretched across your desk. Hey, I will admit it, I am a PowerUser.  As both a Microsoft Certified Trainer, Network Administrator, and PowerShell evangelist, I need real estate.  I often develop my PowerShell code with the ISE and multiple Shell windows.  That way I can code in one, test in another, lookup help files, and test small chunks of code.  The problem comes around to which window is used for what?

Years ago, while visiting a software development company that was acquired by the company that I was working for, I observed one of their techniques for keeping track of which script was running what task.  Each script was monitoring a specific project or log on a server.  Each one of these tasks were assigned a foreground and a background color.  With this in mind, you can set specific foreground and background colors schemes for your development. Tack a look at this code.


Function Switch-HostColor
{
<# ========================================================
    Cmdlet: Switch-HostColor
    Author: Jason A Yoder
    Company: MCTExpert, Inc.
    Version: 1.0
    Date: June 10, 2013
   ======================================================== #>
[CmdletBinding()]
Param ([Parameter(Mandatory=$True)]
       [ValidateSet("RedOnBlack", "BlueOnBlack", "GreenOnBlack",
                    "YellowOnBlack","CyanOnBlack","MagentaOnBlack",
                    "BlackOnBlue")]
       $ColorScheme)
 
    Switch ($ColorScheme)
    {
         "BlueOnBlack"
        {
            $(Get-Host).UI.RawUI.ForegroundColor = "Blue"
            $(Get-Host).UI.RawUI.BackgroundColor = "Black"
        }
        "RedOnBlack"
        {
            $(Get-Host).UI.RawUI.ForegroundColor = "Red"
            $(Get-Host).UI.RawUI.BackgroundColor = "Black"
        }
        "GreenOnBlack"
        {
            $(Get-Host).UI.RawUI.ForegroundColor = "Green"
            $(Get-Host).UI.RawUI.BackgroundColor = "Black"
        }
        "YellowOnBlack"
        {
            $(Get-Host).UI.RawUI.ForegroundColor = "Yellow"
            $(Get-Host).UI.RawUI.BackgroundColor = "Black"
        }
        "CyanOnBlack"
        {
            $(Get-Host).UI.RawUI.ForegroundColor = "Cyan"
            $(Get-Host).UI.RawUI.BackgroundColor = "Black"
        }
        "MagentaOnBlack"
        {
            $(Get-Host).UI.RawUI.ForegroundColor = "Magenta"
            $(Get-Host).UI.RawUI.BackgroundColor = "Black"
        }
        "BlackOnBlue"
        {
            $(Get-Host).UI.RawUI.ForegroundColor = "Black"
            $(Get-Host).UI.RawUI.BackgroundColor = "Blue"
        }
    } # End: Switch ($ColorScheme)
   
    # Clear the host to enable
    Clear-Host
<#
.SYNOPSIS
Change the host color scheme.
 
.DESCRIPTION
Changes the host color scheme to help keep tasks performed in
different shells organized.
 
.PARAMETER ColorScheme
Specify a preset color scheme to change the host foreground and
background colors to.
 
.EXAMPLE
Switch-HostColor -ColorScheme BlueOnBlack
 
Clears the screen and displays all text in blue foreground and
black background.
#>
} # End: Function Switch-HostColor



This code has several defined color formats for you to use as examples.  Notice the use of the ValidateSet parameter attribute.  This provides for tab completion of the possible values for the parameter ColorScheme.  You can provide any color scheme that you wish.  One word of caution, make sure to use two sets of colors that will have a high contrast and not hurt your eyes.  One of the color schemes that I observed in use was magenta text on a bright yellow background.  Not a good idea.
Labels:

Comments

Post a Comment

Popular posts from this blog

Adding a Comment to a GPO with PowerShell

By
As I'm writing this article, I'm also writing a customization for a PowerShell course I'm teaching next week in Phoenix.  This customization deals with Group Policy and PowerShell.  For those of you who attend my classes may already know this, but I sit their and try to ask the questions to myself that others may ask as I present the material.  I finished up my customization a few hours ago and then I realized that I did not add in how to put a comment on a GPO.  This is a feature that many Group Policy Administrators may not be aware of. This past summer I attended a presentation at TechEd on Group Policy.  One organization in the crowd had over 5,000 Group Policies.  In an environment like that, the comment section can be priceless.  I always like to write in the comment section why I created the policy so I know its purpose next week after I've completed 50 other tasks and can't remember what I did 5 minutes ago. In the Group Policy module for PowerShell V3, th
Post a Comment
Read more

Return duplicate values from a collection with PowerShell

By
If you have a collection of objects and you want to remove any duplicate items, it is fairly simple. # Create a collection with duplicate values $Set1 = 1 , 1 , 2 , 2 , 3 , 4 , 5 , 6 , 7 , 1 , 2   # Remove the duplicate values. $Set1 | Select-Object -Unique 1 2 3 4 5 6 7 What if you want only the duplicate values and nothing else? # Create a collection with duplicate values $Set1 = 1 , 1 , 2 , 2 , 3 , 4 , 5 , 6 , 7 , 1 , 2   #Create a second collection with duplicate values removed. $Set2 = $Set1 | Select-Object -Unique   # Return only the duplicate values. ( Compare-Object -ReferenceObject $Set2 -DifferenceObject $Set1 ) . InputObject | Select-Object – Unique 1 2 This works with objects as well as numbers.  The first command creates a collection with 2 duplicates of both 1 and 2.   The second command creates another collection with the duplicates filtered out.  The Compare-Object cmdlet will first find items that are diffe
Post a Comment
Read more

How to list all the AD LDS instances on a server

By
AD LDS allows you to provide directory services to applications that are free of the confines of Active Directory.  To list all the AD LDS instances on a server, follow this procedure: Log into the server in question Open a command prompt. Type dsdbutil and press Enter Type List Instances and press Enter . You will receive a list of the instance name, both the LDAP and SSL port numbers, the location of the database, and its status.
Post a Comment
Read more