<?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/"
		>
<channel>
	<title>Comments on: Windows PowerShell Aliases</title>
	<atom:link href="http://www.powershellpro.com/powershell-tutorial-introduction/tutorial-powershell-aliases/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.powershellpro.com</link>
	<description>Sharing the Experience</description>
	<lastBuildDate>Fri, 03 Feb 2012 08:09:32 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: janu</title>
		<link>http://www.powershellpro.com/powershell-tutorial-introduction/tutorial-powershell-aliases/comment-page-1/#comment-1223</link>
		<dc:creator>janu</dc:creator>
		<pubDate>Fri, 03 Feb 2012 08:09:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.powershellpro.com/powershell-tutorial-introduction/powershell-aliases/#comment-1223</guid>
		<description>It was really great and fun by learning powershell step by step. I love it just because its not theory but practical. It helps me a lot in my project. Thank you so much :)
I have a doubt..
by setting alias thru profile.. how many alias can be added(user defined)?? can u explain adding more alias to the profile?</description>
		<content:encoded><![CDATA[<p>It was really great and fun by learning powershell step by step. I love it just because its not theory but practical. It helps me a lot in my project. Thank you so much <img src='http://www.powershellpro.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /><br />
I have a doubt..<br />
by setting alias thru profile.. how many alias can be added(user defined)?? can u explain adding more alias to the profile?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lori</title>
		<link>http://www.powershellpro.com/powershell-tutorial-introduction/tutorial-powershell-aliases/comment-page-1/#comment-1122</link>
		<dc:creator>Lori</dc:creator>
		<pubDate>Fri, 20 Jan 2012 20:10:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.powershellpro.com/powershell-tutorial-introduction/powershell-aliases/#comment-1122</guid>
		<description>Have you ever seen the behavior where you have the default start folder set but it changes to C:\Windows\system32 when you Run as Administrator?</description>
		<content:encoded><![CDATA[<p>Have you ever seen the behavior where you have the default start folder set but it changes to C:\Windows\system32 when you Run as Administrator?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bill F.</title>
		<link>http://www.powershellpro.com/powershell-tutorial-introduction/tutorial-powershell-aliases/comment-page-1/#comment-664</link>
		<dc:creator>Bill F.</dc:creator>
		<pubDate>Thu, 11 Aug 2011 14:50:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.powershellpro.com/powershell-tutorial-introduction/powershell-aliases/#comment-664</guid>
		<description>Worked great for me!

Excellent Tutorial!

get-service name PowerShellProTutorial

Bill</description>
		<content:encoded><![CDATA[<p>Worked great for me!</p>
<p>Excellent Tutorial!</p>
<p>get-service name PowerShellProTutorial</p>
<p>Bill</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Geoffrey</title>
		<link>http://www.powershellpro.com/powershell-tutorial-introduction/tutorial-powershell-aliases/comment-page-1/#comment-662</link>
		<dc:creator>Geoffrey</dc:creator>
		<pubDate>Tue, 09 Aug 2011 21:05:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.powershellpro.com/powershell-tutorial-introduction/powershell-aliases/#comment-662</guid>
		<description>Thanks so much!

I am hopeless and this series is brilliant.

Cheers</description>
		<content:encoded><![CDATA[<p>Thanks so much!</p>
<p>I am hopeless and this series is brilliant.</p>
<p>Cheers</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robert</title>
		<link>http://www.powershellpro.com/powershell-tutorial-introduction/tutorial-powershell-aliases/comment-page-1/#comment-641</link>
		<dc:creator>Robert</dc:creator>
		<pubDate>Wed, 15 Jun 2011 00:50:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.powershellpro.com/powershell-tutorial-introduction/powershell-aliases/#comment-641</guid>
		<description>Dont bother hacking the registry.

Right click the powershell shortcut on your desktop. Click advanced, click run as administrator.

Works for most any shortcut.</description>
		<content:encoded><![CDATA[<p>Dont bother hacking the registry.</p>
<p>Right click the powershell shortcut on your desktop. Click advanced, click run as administrator.</p>
<p>Works for most any shortcut.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter Wood</title>
		<link>http://www.powershellpro.com/powershell-tutorial-introduction/tutorial-powershell-aliases/comment-page-1/#comment-587</link>
		<dc:creator>Peter Wood</dc:creator>
		<pubDate>Tue, 15 Mar 2011 14:17:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.powershellpro.com/powershell-tutorial-introduction/powershell-aliases/#comment-587</guid>
		<description>Great tutorial! Thanks for the help!</description>
		<content:encoded><![CDATA[<p>Great tutorial! Thanks for the help!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kyle</title>
		<link>http://www.powershellpro.com/powershell-tutorial-introduction/tutorial-powershell-aliases/comment-page-1/#comment-586</link>
		<dc:creator>Kyle</dc:creator>
		<pubDate>Mon, 14 Mar 2011 04:44:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.powershellpro.com/powershell-tutorial-introduction/powershell-aliases/#comment-586</guid>
		<description>At first the &quot;Run as Administrator&quot; technique didn&#039;t work for me.  I guess it does for many out there but if not, as a permanent fix you can add the permission in directly via the windows registry.  It&#039;s pretty easy and eliminates the need to &quot;run as admin&quot;.

See http://kyleclegg.com/powershell/

Hope this helps someone!</description>
		<content:encoded><![CDATA[<p>At first the &#8220;Run as Administrator&#8221; technique didn&#8217;t work for me.  I guess it does for many out there but if not, as a permanent fix you can add the permission in directly via the windows registry.  It&#8217;s pretty easy and eliminates the need to &#8220;run as admin&#8221;.</p>
<p>See <a href="http://kyleclegg.com/powershell/" rel="nofollow">http://kyleclegg.com/powershell/</a></p>
<p>Hope this helps someone!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JohnnyB</title>
		<link>http://www.powershellpro.com/powershell-tutorial-introduction/tutorial-powershell-aliases/comment-page-1/#comment-581</link>
		<dc:creator>JohnnyB</dc:creator>
		<pubDate>Tue, 22 Feb 2011 21:27:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.powershellpro.com/powershell-tutorial-introduction/powershell-aliases/#comment-581</guid>
		<description>:Dennis
I open powershell with ps directly from run (Win-logo R)
In the registry create new key at
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\ps.exe 
with value
C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe

does the trick?</description>
		<content:encoded><![CDATA[<p> <img src='http://www.powershellpro.com/wp-includes/images/smilies/icon_biggrin.gif' alt=':D' class='wp-smiley' /> ennis<br />
I open powershell with ps directly from run (Win-logo R)<br />
In the registry create new key at<br />
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\ps.exe<br />
with value<br />
C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe</p>
<p>does the trick?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JohnnyB</title>
		<link>http://www.powershellpro.com/powershell-tutorial-introduction/tutorial-powershell-aliases/comment-page-1/#comment-580</link>
		<dc:creator>JohnnyB</dc:creator>
		<pubDate>Tue, 22 Feb 2011 21:26:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.powershellpro.com/powershell-tutorial-introduction/powershell-aliases/#comment-580</guid>
		<description>@Dennis
I open powershell with ps directly from run (Win-logo R)
In the registry create new key at
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\ps.exe 
with value
C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe

does the trick?</description>
		<content:encoded><![CDATA[<p>@Dennis<br />
I open powershell with ps directly from run (Win-logo R)<br />
In the registry create new key at<br />
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\ps.exe<br />
with value<br />
C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe</p>
<p>does the trick?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jai-Jay</title>
		<link>http://www.powershellpro.com/powershell-tutorial-introduction/tutorial-powershell-aliases/comment-page-1/#comment-578</link>
		<dc:creator>Jai-Jay</dc:creator>
		<pubDate>Thu, 17 Feb 2011 15:44:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.powershellpro.com/powershell-tutorial-introduction/powershell-aliases/#comment-578</guid>
		<description>Great tutorials!
What if I want keep profile in my working directory (somewhere on D:) and open PowerShell with customised-personalised profile? Is it possible?</description>
		<content:encoded><![CDATA[<p>Great tutorials!<br />
What if I want keep profile in my working directory (somewhere on D:) and open PowerShell with customised-personalised profile? Is it possible?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

