Unabridged Excerpts from C# and T-SQL Code

March 21, 2015 at 02:21PM

2015-03-21T14:21:00.001-05:00

Photo taken on March 21, 2015 at 02:21PM

via Do Camera http://ift.tt/1AXo6LJ

This is a test

2015-03-21T13:51:00.001-05:00

This is a test

March 21, 2015 at 04:30AM

2015-03-21T04:30:00.001-05:00

Photo taken on March 21, 2015 at 04:30AM

via Do Camera http://ift.tt/1AUxX55

March 21, 2015 at 04:29AM

2015-03-21T04:29:00.001-05:00

Photo taken on March 21, 2015 at 04:29AM

via Do Camera http://ift.tt/1Bgxr0w

March 21, 2015 at 12:13AM

2015-03-21T00:13:00.001-05:00

Photo taken on March 21, 2015 at 12:13AM

via Do Camera http://ift.tt/1BfBzxC

March 17, 2015 at 11:00PM

2015-03-17T23:01:00.001-05:00

Photo taken on March 17, 2015 at 11:00PM

via Do Camera http://ift.tt/1BSp13S

March 17, 2015 at 11:00PM

2015-03-17T23:00:00.003-05:00

Photo taken on March 17, 2015 at 11:00PM

via Do Camera http://ift.tt/1O4pp4F

March 17, 2015 at 11:00PM

2015-03-17T23:00:00.001-05:00

Photo taken on March 17, 2015 at 11:00PM

via Do Camera http://ift.tt/1ADeBkK

PowerShell Workflow for Mere Mortals: Part 5

2013-10-04T04:22:00.001-05:00

TechNet Blogs by The Scripting Guys
Summary: Microsoft Scripting Guy, Ed Wilson, concludes his five-part series about Windows PowerShell Workflow.

Hey, Scripting Guy! I have a number of commands that I want to run against several remote servers. The commands include stuff that must happen prior to something else happening. But then, there are also some things that I would like to happen as fast as possible. Is this permissible? If so, do I have to write two different workflows?

—TB

Hello TB,

Microsoft Scripting Guy, Ed Wilson, is here. This afternoon I am sipping an awesome cup of Oolong tea with a cinnamon stick, jasmine flower, and lemon grass. The flavor is just about perfect. In the background, I am listening to Ravel. Outside, the sky is dark and it is raining. The thunder seems to punctuate the music.

Note This is the last post in a five-part series about Windows PowerShell Workflow for “mere mortals.” Before you read this post, please read:

PowerShell Workflow for Mere Mortals: Part 1
PowerShell Workflow for Mere Mortals: Part 2
PowerShell Workflow for Mere Mortals: Part 3
PowerShell Workflow for Mere Mortals: Part 4
For more information about workflow, see these Hey, Scripting Guy! Blog posts: Windows PowerShell Workflow.

Well TB, the good news is that you do not need to write two different workflows to enable parallel processing and sequential processing. Windows PowerShell Workflows are flexible enough to handle both in the same workflow.

Adding a sequence activity to a workflow

To add a sequence activity to a Windows PowerShell Workflow, all I need to do is use the Sequence keyword and specify a script block. When I do this, it causes the commands in the sequence script block to run sequentially and in the specified order.

The key concept here is that a Sequence activity occurs within a Parallel activity. The Sequence activity is required when I want commands to run in a particular order. This is because commands running inside a Parallel activity run in an undetermined order.

The commands in the Sequence script block run in parallel with all of the commands in the Parallel activity. But the commands within the Sequence script block run in the order in which they appear in the script block. The following workflow illustrates this technique:

workflow get-winfeatures

{

Parallel {

Get-WindowsFeature -Name PowerShell*

InlineScript {$env:COMPUTERNAME}

Sequence {

Get-date

$PSVersionTable.PSVersion } }

}

In the previous workflow, the order for Get-WindowsFeature, the inline script, and the Sequence activity is not determined. The only thing I know for sure is that the Get-Date command runs before I obtain the PSVersion because this is the order that I specified in the Sequence activity script block.

To run my workflow, I first run the PS1 script that contains the workflow. Next, I call the workflow and I pass two computer names to it via the PSComputerName automatic parameter. Here is my command:

get-winfeatures -PSComputerName server1, server2

The image that follows shows the Windows PowerShell ISE where I call the workflow. It also illustrates the order in which the commands ran this time. Note that the commands in the Sequence script block ran in the specified order—that is, Get-Date executed before $PsVersionTable.PSVersion. Also notice that they were in the same Parallel stream of execution.

Some workflow coolness

One of the cool things about this workflow, is that I ran it from my laptop running Windows 8. What is so cool about that? Well, the Get-WindowsFeature cmdlet does not work on desktop operating systems. Therefore, I ran a command from my laptop—a command which does not exist on my laptop, but it does exist on the target computers, Server1 and Server2.

Another cool workflow feature is the InlineScript activity. I am able to access an environmental variable from the remote servers. The InlineScript activity allows me to do things that otherwise would not be permitted in a Windows PowerShell Workflow. It adds a lot of flexibility.

TB, that is all there is to using Windows PowerShell Workflow and specifying Sequence information. This concludes Windows PowerShell Workflow week. Join me tomorrow when I will talk about Active Directory with Windows PowerShell.

I invite you to follow me on Twitter and Facebook. If you have any questions, send email to me at scripter@microsoft.com, or post your questions on the Official Scripting Guys Forum. See you tomorrow. Until then, peace.

Ed Wilson, Microsoft Scripting Guy

TechNet Blogs by The Scripting Guys
◆

Dauphine: A Ferriday for the 21st century

2013-09-14T20:37:00.001-05:00

There was little in most of the life of our father that would indicate his historical importance. Most of his life was spent as frankly a under achieving drifting through his life from one day to the next. We know better. Much has been written about him and his work. On the 30th anniversary of his death, we his children want the the world and posterity to know the real John Dauphine. All his faults and all his goodness. How thoughts and ideas that he jealously kept locked in his head for most of his adult were almost lost to the world. How if it were not for his sure knowledge of his own impedending death he would have never set down the theoretical foundations of Washington-Yang theory. Washington-Yang ultimately proved the grand unified theory that had the dream of scientists since Einstein. Though he could have only dreamed it our father changed human history.

Not bad for black kid from New Orleans.

WPF based ORM

2012-04-15T16:51:00.001-05:00

Finally got WPF gui for code generator to kinda work the way that I what it to. Attached are some screenshots (elementary I know).

Unabridged Excerpts from C# and T-SQL Code

March 21, 2015 at 02:21PM

This is a test

March 21, 2015 at 04:30AM

March 21, 2015 at 04:29AM

March 21, 2015 at 12:13AM

March 17, 2015 at 11:00PM

March 17, 2015 at 11:00PM

March 17, 2015 at 11:00PM

PowerShell Workflow for Mere Mortals: Part 5

Dauphine: A Ferriday for the 21st century

WPF based ORM

Untitled

@JeffersonObama, 3/30/12 8:01 PM

My first Snowball in years

Kicked off house floor for wearing hoodie

Lunch! Right of the grill

Dennis Rodman...broke...

This is why I like Obamacare

So now Obama supporters cross out the n in "nobama 2012". Can't we all just get along? At least in the Starbucks bathroom?

Opinion: Why Etch A Sketch gibe will be hard for Romney to shake.

Steve Jobs Tried to Hire Linux Creator Linus Torvalds to Work on OS X - MacRumors.com

Hate the New Apple TV UI? So Did Steve Jobs, Allegedly | News & Opinion | PCMag.com

Article: The History of Jim Crow

New iPad Too Hot to Handle? Users Report Burning Temperatures - ABC News

Checkout the download speed that I'm getting on the LTE ipad with 3 bars!