﻿<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/">
  <channel>
    <title>Joe Brinkman (ASP.Net MVP)</title>
    <description>A discussion of PowerShell and Asp.Net</description>
    <link>http://www.powershellcommunity.org/Blogs/CommunityBlogs/tabid/55/BlogId/4/Default.aspx</link>
    <language>en-US</language>
    <managingEditor>joe.brinkman@dotnetnuke.com</managingEditor>
    <webMaster>do-not-reply@powershellcommunity.org</webMaster>
    <pubDate>Tue, 06 Jan 2009 01:41:20 GMT</pubDate>
    <lastBuildDate>Tue, 06 Jan 2009 01:41:20 GMT</lastBuildDate>
    <docs>http://backend.userland.com/rss</docs>
    <generator>Blog RSS Generator Version 3.4.0.39853</generator>
    <item>
      <title>PowerShell and SubSonic</title>
      <description>PowerShell is the perfect tool for wrapping complex command-line tools.  By simplifying the API and using the built in Tab expansion capability, PowerShell makes even the most cumbersome commands usable without giving up any of their power.  In this example we'll look at how I converted a batch file for SubSonic to a PowerShell script.</description>
      <link>http://www.powershellcommunity.org/Blogs/CommunityBlogs/tabid/55/EntryID/64/Default.aspx</link>
      <author>joe.brinkman@dotnetnuke.com</author>
      <comments>http://www.powershellcommunity.org/Blogs/CommunityBlogs/tabid/55/EntryID/64/Default.aspx#Comments</comments>
      <guid isPermaLink="true">http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=64</guid>
      <pubDate>Tue, 01 Jan 2008 23:42:33 GMT</pubDate>
      <slash:comments>0</slash:comments>
      <trackback:ping>http://www.powershellcommunity.org/DesktopModules/Blog/Trackback.aspx?id=64</trackback:ping>
    </item>
    <item>
      <title>Creating a management dashboard with PowerGadgets and PowerShell</title>
      <description>Several months ago I stumbled upon &lt;a href="http://www.powergadgets.com/"&gt;PowerGadgets&lt;/a&gt; and have been finding more and more uses for it ever since.  I was initially intrigued by the ability to run powershell scripts but didn't have any immediate needs that required that much power.  One of the strengths of PowerGadgets is the ability to run database queries and then to present the data using very slick graphs, guages and maps.</description>
      <link>http://www.powershellcommunity.org/Blogs/CommunityBlogs/tabid/55/EntryID/54/Default.aspx</link>
      <author>joe.brinkman@dotnetnuke.com</author>
      <comments>http://www.powershellcommunity.org/Blogs/CommunityBlogs/tabid/55/EntryID/54/Default.aspx#Comments</comments>
      <guid isPermaLink="true">http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=54</guid>
      <pubDate>Sun, 16 Dec 2007 23:30:51 GMT</pubDate>
      <slash:comments>0</slash:comments>
      <trackback:ping>http://www.powershellcommunity.org/DesktopModules/Blog/Trackback.aspx?id=54</trackback:ping>
    </item>
    <item>
      <title>Why not just use Add-Member</title>
      <description>&lt;p&gt;In my last post &lt;a href="http://blog.theaccidentalgeek.com/archive/2007/10/16/getting-a-usernamepassword-in-powershell.aspx"&gt;Getting a Username/Password in PowerShell&lt;/a&gt; (cross posted to &lt;a href="http://www.powershellcommunity.org/Home/tabid/36/EntryID/5/Default.aspx"&gt;PowerShellCommunity.org&lt;/a&gt;), I was asked why not just use the Add-Member cmdlet.  Having been doing software development for my entire adult life, this is not the first time this question has come up.  Ok.  Maybe not those exact words, but something very similar - why use code X when code Y does the same thing.  Where I come from there is really only one response to this - look at both code alternatives and determine which one is the most efficient at doing the job without also becoming a maintenance problem.  So lets take a peek under the hood a bit so we can see why I chose PSObject.Members.Add over using the Add-Member cmdlet.&lt;/p&gt;</description>
      <link>http://www.powershellcommunity.org/Blogs/CommunityBlogs/tabid/55/EntryID/8/Default.aspx</link>
      <author>joe.brinkman@dotnetnuke.com</author>
      <comments>http://www.powershellcommunity.org/Blogs/CommunityBlogs/tabid/55/EntryID/8/Default.aspx#Comments</comments>
      <guid isPermaLink="true">http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=8</guid>
      <pubDate>Fri, 19 Oct 2007 14:13:58 GMT</pubDate>
      <slash:comments>1</slash:comments>
      <trackback:ping>http://www.powershellcommunity.org/DesktopModules/Blog/Trackback.aspx?id=8</trackback:ping>
    </item>
    <item>
      <title>Getting a Username/Password in PowerShell</title>
      <description>&lt;p&gt;As part of getting ready for my PowerShell session at &lt;a href="http://www.openforce07.com" title="OpenForce '07 Conference"&gt;OpenForce '07&lt;/a&gt;, I am creating a set of helper functions for working with SMO to manipulate and query the database server.  A common need when working with the database is to pass the username and password to various SMO methods.  When I first started coding my examples, I just passed a username and password as parameters into my functions.  This works, but does not exactly look professional when you are sitting in a presentation and typing out passwords in plaintext.&lt;/p&gt;</description>
      <link>http://www.powershellcommunity.org/Blogs/CommunityBlogs/tabid/55/EntryID/5/Default.aspx</link>
      <author>joe.brinkman@dotnetnuke.com</author>
      <comments>http://www.powershellcommunity.org/Blogs/CommunityBlogs/tabid/55/EntryID/5/Default.aspx#Comments</comments>
      <guid isPermaLink="true">http://www.powershellcommunity.org/Default.aspx?tabid=55&amp;EntryID=5</guid>
      <pubDate>Fri, 19 Oct 2007 14:12:40 GMT</pubDate>
      <slash:comments>5</slash:comments>
      <trackback:ping>http://www.powershellcommunity.org/DesktopModules/Blog/Trackback.aspx?id=5</trackback:ping>
    </item>
  </channel>
</rss>