A scare

My wife told me something scary.

We were cooking some eggs on our gas stove last night to add to our dinner.  We had the fire on the smallest setting.

Apparently we both forgot to turn it off.

When she woke up and went to the kitchen, she was surprised the kitchen is somewhat warm (usually it's freezing cold in the morning).  To her horror, the flame was still going on the stove.  She quickly turn it off.

We give thanks to the Lord that nothing had happened to us during the evening.  It was very scary.

We do have a smoke alarm, but the gas-stove was going on the smallest setting and gives off no smoke, so the alarm didn't go off.  The window was also slighly open so that the kitchen had fresh air.

Something Mark Dasco and I dug up

I'm just going to blog it so I don't need to remember it.

powershell -nologo -command "& {c:\test.ps1}"

executes the powershell script from old command prompt (or scheduled tasks).

PowerShell script for rebuilding ASP.NET

# build
msbuild /t:Rebuild /v:q
# kill aspnet
get-process aspnet_wp | kill
# reset iis
iisreset
# clear log4net logs
del -force c:\logs\*.*
# poke the webpage so that IIS/ASP.NET will load the webapp
get-url http://localhost/TestProject/TestPage.aspx | out-null

You'll need the Power Shell Community Extensions for the last get-url cmdlet.

Transformers

I realized what I need.

A transformers desktop.

When you double click a folder, it does a massive transformation sequence to open up!

:-D

The movie broke $125 million for opening week, made record for a "non-sequel" film beating even Spiderman back in its day.

Now I can rest, because there's going to be a Transformers 2 now!

A "which command" cmdlet script

PS C:\> (get-item env:path).value.split("") | where { $_ -ne "" } | where { test-path( join-path $_ "msbuild.exe" ) }

C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727

Next task, make it a parameterized cmdlet