<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: PowerShell Quick Tip: Create aliases to facilitate invocation of PowerShell script (ps1) files</title>
	<atom:link href="http://poshoholic.com/2009/02/04/powershell-quick-tip-create-aliases-to-facilitate-invocation-of-powershell-script-ps1-files/feed/" rel="self" type="application/rss+xml" />
	<link>http://poshoholic.com/2009/02/04/powershell-quick-tip-create-aliases-to-facilitate-invocation-of-powershell-script-ps1-files/</link>
	<description>Totally addicted to PowerShell</description>
	<lastBuildDate>Sat, 05 May 2012 13:03:31 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Poshoholic</title>
		<link>http://poshoholic.com/2009/02/04/powershell-quick-tip-create-aliases-to-facilitate-invocation-of-powershell-script-ps1-files/#comment-935</link>
		<dc:creator><![CDATA[Poshoholic]]></dc:creator>
		<pubDate>Thu, 12 Feb 2009 13:47:20 +0000</pubDate>
		<guid isPermaLink="false">http://kirkmunro.wordpress.com/2009/02/04/powershell-quick-tip-create-aliases-to-facilitate-invocation-of-powershell-script-ps1-files/#comment-935</guid>
		<description><![CDATA[There isn&#039;t any more maintenance with this technique.  Well, sure, if you compare it to using a folder in your path variable, then it is a little more work.  But when compared to using a series of library files, you can still create the library file which creates the aliases to your scripts and then dot source those files.

The biggest benefit I have found for me with this method is that it allows me to make modifications to functions (something that I do *a lot*) and get those changes immediately in PowerShell without needing to dot source the file.  Again, if I had a scripts folder in my path this wouldn&#039;t be necessary, but I&#039;ve broken my script library up into subfolders and don&#039;t want to have to modify my path each time I add a new folder to that script library.

Lastly, this works well when transferring scripts to other machines where PowerShell is installed because you can set up a base path and then build your relative script paths from that, move to a new machine, make one change if necessary (the base path), and then you can use your scripts there.  For some reason this is an easier thought process to me than worrying about the path environment variable.

Anyhow, as with everything PowerShell, this isn&#039;t the single best method by any means.  It&#039;s simply the one I&#039;ve adopted because I found it works best for me.

Kirk out.]]></description>
		<content:encoded><![CDATA[<p>There isn&#8217;t any more maintenance with this technique.  Well, sure, if you compare it to using a folder in your path variable, then it is a little more work.  But when compared to using a series of library files, you can still create the library file which creates the aliases to your scripts and then dot source those files.</p>
<p>The biggest benefit I have found for me with this method is that it allows me to make modifications to functions (something that I do *a lot*) and get those changes immediately in PowerShell without needing to dot source the file.  Again, if I had a scripts folder in my path this wouldn&#8217;t be necessary, but I&#8217;ve broken my script library up into subfolders and don&#8217;t want to have to modify my path each time I add a new folder to that script library.</p>
<p>Lastly, this works well when transferring scripts to other machines where PowerShell is installed because you can set up a base path and then build your relative script paths from that, move to a new machine, make one change if necessary (the base path), and then you can use your scripts there.  For some reason this is an easier thought process to me than worrying about the path environment variable.</p>
<p>Anyhow, as with everything PowerShell, this isn&#8217;t the single best method by any means.  It&#8217;s simply the one I&#8217;ve adopted because I found it works best for me.</p>
<p>Kirk out.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: halr9000</title>
		<link>http://poshoholic.com/2009/02/04/powershell-quick-tip-create-aliases-to-facilitate-invocation-of-powershell-script-ps1-files/#comment-934</link>
		<dc:creator><![CDATA[halr9000]]></dc:creator>
		<pubDate>Thu, 12 Feb 2009 03:50:49 +0000</pubDate>
		<guid isPermaLink="false">http://kirkmunro.wordpress.com/2009/02/04/powershell-quick-tip-create-aliases-to-facilitate-invocation-of-powershell-script-ps1-files/#comment-934</guid>
		<description><![CDATA[The only problem I have with this technique is maintenance.  I like to just toss all my scripts into a folder which is in my $env:path, or, toss functions into a series of library files which are dot-sourced automatically in my profile.]]></description>
		<content:encoded><![CDATA[<p>The only problem I have with this technique is maintenance.  I like to just toss all my scripts into a folder which is in my $env:path, or, toss functions into a series of library files which are dot-sourced automatically in my profile.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Use PowerShell &#187; ConvertTo-Function</title>
		<link>http://poshoholic.com/2009/02/04/powershell-quick-tip-create-aliases-to-facilitate-invocation-of-powershell-script-ps1-files/#comment-929</link>
		<dc:creator><![CDATA[Use PowerShell &#187; ConvertTo-Function]]></dc:creator>
		<pubDate>Wed, 04 Feb 2009 21:28:57 +0000</pubDate>
		<guid isPermaLink="false">http://kirkmunro.wordpress.com/2009/02/04/powershell-quick-tip-create-aliases-to-facilitate-invocation-of-powershell-script-ps1-files/#comment-929</guid>
		<description><![CDATA[[...] Munro (@poshoholic) pointed out that aliases (and expands on it in this blog post) might be an easier way to go.  That would definitely be an [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Munro (@poshoholic) pointed out that aliases (and expands on it in this blog post) might be an easier way to go.  That would definitely be an [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

