<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Windows PowerShell (Monad) Has Arrived</title><link>http://blogs.msdn.com/monad/archive/2006/04/25/583333.aspx</link><description>I just got out of Bob Muglia's keynote speech where he formally announced Windows PowerShell (previously known as Monad). The key things he announced are: Monad (MSH) has a new name: Windows PowerShell Windows PowerShell will RTW (Web download) in Q4</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: Windows PowerShell (Monad) Has Arrived</title><link>http://blogs.msdn.com/monad/archive/2006/04/25/583333.aspx#583373</link><pubDate>Tue, 25 Apr 2006 20:45:37 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:583373</guid><dc:creator>/\/\o\/\/</dc:creator><description>With the move to the new blog the &amp;quot;Did you Know&amp;quot; series did disapear.&lt;br&gt;&lt;br&gt;Greetings /\/\o\/\/&lt;br&gt;&lt;br&gt;PS I'm commenting this on the Old blog as comments seem to be disabled at the new one.&lt;br&gt;</description></item><item><title>Unicode support</title><link>http://blogs.msdn.com/monad/archive/2006/04/25/583333.aspx#583445</link><pubDate>Tue, 25 Apr 2006 22:02:06 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:583445</guid><dc:creator>Cory</dc:creator><description>Will we ever get a Monad that doesn't run in cmd.exe? &amp;nbsp;I want to be able to enter Unicode like Japanese.</description></item><item><title>Microsoft Management Summit 2006: A Power Supply in Every Pot &amp;amp;#38; First Impressions</title><link>http://blogs.msdn.com/monad/archive/2006/04/25/583333.aspx#583541</link><pubDate>Tue, 25 Apr 2006 23:57:29 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:583541</guid><dc:creator>People Over Process</dc:creator><description>I'm at the Microsoft Management Summit this week in San Diego. As promised, I won't be throwing up my raw notes, especially since yesterday's notes are 16 pages of scribbles on the conference provided paper. Juice for the Foot-long Why's...</description></item><item><title>re: Windows PowerShell (Monad) Has Arrived</title><link>http://blogs.msdn.com/monad/archive/2006/04/25/583333.aspx#583565</link><pubDate>Wed, 26 Apr 2006 00:28:10 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:583565</guid><dc:creator>Morgan</dc:creator><description>From the release notes...&lt;br&gt;&lt;br&gt;&amp;quot;Msh.exe&amp;quot; is now replaced with &amp;quot;PowerShell.exe&amp;quot;&lt;br&gt;&lt;br&gt;WHY OH WHY?!? &lt;br&gt;&lt;br&gt;Can't you use psh.exe instead? &lt;br&gt;</description></item><item><title>re: Windows PowerShell (Monad) Has Arrived</title><link>http://blogs.msdn.com/monad/archive/2006/04/25/583333.aspx#583567</link><pubDate>Wed, 26 Apr 2006 00:30:21 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:583567</guid><dc:creator>Morgan</dc:creator><description>Like Cory I am also interested in when it will be a seperate application and not a console based application. I understand this is planned but will it be like this for the final release? We are getting very close now we are at RC1 and I would like to see the console application be left behind replaced by its own interface so we can better utilise things such as unicode without the need for ugly escape sequences.</description></item><item><title>re: Windows PowerShell (Monad) Has Arrived</title><link>http://blogs.msdn.com/monad/archive/2006/04/25/583333.aspx#583570</link><pubDate>Wed, 26 Apr 2006 00:33:14 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:583570</guid><dc:creator>Monad Team</dc:creator><description>&amp;gt; Can't you use psh.exe instead? &lt;br&gt;You can create your own shortcut psh.bat to call PowerShell.exe&lt;br&gt;&lt;br&gt;Jeffrey Snover </description></item><item><title>re: Windows PowerShell (Monad) Has Arrived</title><link>http://blogs.msdn.com/monad/archive/2006/04/25/583333.aspx#583573</link><pubDate>Wed, 26 Apr 2006 00:38:55 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:583573</guid><dc:creator>Morgan</dc:creator><description>&amp;gt;You can create your own shortcut psh.bat to call PowerShell.exe&lt;br&gt;&lt;br&gt;Yes I could be on system that are not setup like that I will have to either type out powershell.exe or created psh.bat to call powershell.exe for me. That is rather annoying. The thing I like about cmd.exe is that it is consistent on every Windows machine, even the ones I have not setup. </description></item><item><title>re: Windows PowerShell (Monad) Has Arrived</title><link>http://blogs.msdn.com/monad/archive/2006/04/25/583333.aspx#583580</link><pubDate>Wed, 26 Apr 2006 00:48:36 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:583580</guid><dc:creator>Monad Team</dc:creator><description>&amp;gt; Will we ever get a Monad that doesn't run in cmd.exe? &amp;nbsp;I want to be able to enter Unicode like Japanese.&lt;br&gt;We don't plan to ship this in V1. &amp;nbsp;I belive that Karl Prosser's MSHAnalyzer supports this. &amp;nbsp;Check it out:&lt;br&gt;&lt;a rel="nofollow" target="_new" href="http://www.karlprosser.com/coder/?cat=8"&gt;http://www.karlprosser.com/coder/?cat=8&lt;/a&gt;&lt;br&gt;&lt;br&gt;Jeffrey Snover</description></item><item><title>re: Did You Know Series</title><link>http://blogs.msdn.com/monad/archive/2006/04/25/583333.aspx#583628</link><pubDate>Wed, 26 Apr 2006 02:11:15 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:583628</guid><dc:creator>Monad Team</dc:creator><description>MoW -- looks like the series made it in there to me: &lt;a rel="nofollow" target="_new" href="http://blogs.msdn.com/powershell/archive/2006/04/25/583218.aspx"&gt;http://blogs.msdn.com/powershell/archive/2006/04/25/583218.aspx&lt;/a&gt;&lt;br&gt;&lt;br&gt;Lee</description></item><item><title>re: Windows PowerShell (Monad) Has Arrived</title><link>http://blogs.msdn.com/monad/archive/2006/04/25/583333.aspx#583650</link><pubDate>Wed, 26 Apr 2006 02:35:19 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:583650</guid><dc:creator>DontBotherMeWithSpam</dc:creator><description>Happy Birthday, PowerShell! &amp;nbsp;Congrats~ Powershell Team~</description></item><item><title>re: Windows PowerShell (Monad) Has Arrived</title><link>http://blogs.msdn.com/monad/archive/2006/04/25/583333.aspx#583653</link><pubDate>Wed, 26 Apr 2006 02:39:30 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:583653</guid><dc:creator>Morgan</dc:creator><description>Well after playing around with it for a while... I LOVE IT!&lt;br&gt;&lt;br&gt;What an awesome, awesome shell. It is so nice to use. Thank you, thank you, thank you!&lt;br&gt;&lt;br&gt;Now if you will just rename the exe to psh.exe all will be perfect ;)&lt;br&gt;&lt;br&gt;PS Not bad if my only complaint is the name of the exe ;)</description></item><item><title>re: Windows PowerShell (Monad) Has Arrived</title><link>http://blogs.msdn.com/monad/archive/2006/04/25/583333.aspx#583855</link><pubDate>Wed, 26 Apr 2006 09:26:19 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:583855</guid><dc:creator>Nektar</dc:creator><description>Please rename the executable to psh from powershell. The commandline should have short name and not long ones.&lt;br&gt;Also, when you say that the next wave of products will utilize it which wave are you talking about? Longhorn server? Or the wave after Longhorn server ie. the one coming around 2010 or there abouts. If so, then too late.</description></item><item><title>re: Windows PowerShell (Monad) Has Arrived</title><link>http://blogs.msdn.com/monad/archive/2006/04/25/583333.aspx#583858</link><pubDate>Wed, 26 Apr 2006 09:29:44 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:583858</guid><dc:creator>Anon</dc:creator><description>Why won't it be included with Vista? Even if Vista admin uis are not integrated with it, why won't you include it in the os alongside all the other system tools. If you want Powershell to be a success then you should put it in Vista, otherwise tough luck. If you want to help admins then what better way than having this powerful shell with every default Windows installation. They will not needlessly have to install it on every computer.</description></item><item><title>Back on track!</title><link>http://blogs.msdn.com/monad/archive/2006/04/25/583333.aspx#583861</link><pubDate>Wed, 26 Apr 2006 09:33:09 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:583861</guid><dc:creator>Erno de Weerd</dc:creator><description /></item><item><title>re: Windows PowerShell (Monad) Has Arrived</title><link>http://blogs.msdn.com/monad/archive/2006/04/25/583333.aspx#583932</link><pubDate>Wed, 26 Apr 2006 11:43:02 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:583932</guid><dc:creator>Nick</dc:creator><description>I really agree with getting the EXE renamed to psh.exe. Having to type out 'powershell' is totally obnoxious after years of cmd and more recently msh. PLEASE change this. I consider it a bug (waste of typing)&lt;br&gt;&lt;br&gt;It's embarassing enough that it's called PowerShell in the first place, but we can get over that in time :)</description></item><item><title>re: Windows PowerShell (Monad) Has Arrived</title><link>http://blogs.msdn.com/monad/archive/2006/04/25/583333.aspx#583940</link><pubDate>Wed, 26 Apr 2006 12:01:28 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:583940</guid><dc:creator>Nick</dc:creator><description>Or perhaps more appropriately at this point in the game since powershell.exe is probably baked into too many things, you could add a second exe, psh.exe, whos sole purpose is to invoke powershell.exe with the same parameters... that seems like a non-breaking win for everyone's opinion. It just needs to come as part of the official install or it's not worth it.</description></item><item><title>re: Windows PowerShell (Monad) Has Arrived</title><link>http://blogs.msdn.com/monad/archive/2006/04/25/583333.aspx#584095</link><pubDate>Wed, 26 Apr 2006 16:19:32 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:584095</guid><dc:creator>Mike</dc:creator><description>Shells time long passed. Now people are moving to graphical interfaces instead. It's called progress but Microsoft is having none of it. If this new and improved command.com came out 15 years ago it would have meant something. But now ? Who do you think has enough time and patience to work with a command line version of the graphical tools already available?</description></item><item><title>re: Windows PowerShell (Monad) Has Arrived</title><link>http://blogs.msdn.com/monad/archive/2006/04/25/583333.aspx#584180</link><pubDate>Wed, 26 Apr 2006 17:59:13 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:584180</guid><dc:creator>Monad Team</dc:creator><description>&amp;gt; Shells time long passed. &lt;br&gt;I beg to differ with you my friend. &amp;nbsp;There is a rebirth of CLI in progress. &amp;nbsp;I point you to the DMTF SMASH work as an example. &amp;nbsp;&lt;br&gt;&lt;br&gt;In the end, we don't have to agree and there also isn't much of to disagree with either. &amp;nbsp;No one is a bigger fan of GUIs that me. &amp;nbsp;If fact the PowerShell team and the MMC team are now the same team. &amp;nbsp;&lt;br&gt;&lt;br&gt;PowerShell is architected to allow rich GUIs to be layered on top of it. &amp;nbsp;We fully expect a good number of users to use the GUI exclusively - that is fine. &amp;nbsp;We full expect many users to use the GUI and then want to automation that operation so they'll want the GUI to tell them what commands they should type (this is one of the key benefits of this layering). &amp;nbsp;We also expect many users to primarily use the CLI and occassionaly use the GUI. &amp;nbsp;Dude - there is no wrong answer here - it is all flavors of wonderful. &amp;nbsp;The big change is that in the past, the CLI did not have parity with the GUI. &amp;nbsp;We are fixing that. &amp;nbsp;If you are content with the GUI - happy days all around.&lt;br&gt;&lt;br&gt;Now all that said, I'll just point out one thing. &amp;nbsp;GUIs by their nature, codify an experience. &amp;nbsp;CLIs do so to a much lesser extent. &amp;nbsp;If that experience is what you want - you're golden. &amp;nbsp;If it isn't, you often don't have many choices. &amp;nbsp;With a CLI, the entire point of it is that you can create exactly the experience you want and need. &amp;nbsp;Yes that requires effort on your part because you have to think about what you want and then express it. &amp;nbsp;With PowerShell, we are trying to make it very simple for you to express whatever experience you want as easily as possible so: &amp;nbsp;You think it. &amp;nbsp;You type it. You get it.&lt;br&gt;&lt;br&gt;Enjoy!&lt;br&gt;Jeffrey Snover</description></item><item><title>re: Windows PowerShell (Monad) Has Arrived</title><link>http://blogs.msdn.com/monad/archive/2006/04/25/583333.aspx#584407</link><pubDate>Wed, 26 Apr 2006 21:33:58 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:584407</guid><dc:creator>Thanateros</dc:creator><description>Seems to me that Microsoft's Marketing is starting to act the same way Digital's marketing folks did. &amp;nbsp;They just don't get it. &amp;nbsp;Does the product HAVE to have a cool sounding name? No. &amp;nbsp;Make a product that works and we will use it regardless of the name. &amp;nbsp;This also seems to me like someone thought that MSH was too much like UNIX Shell naming and we can't have that at Microsoft now can we...</description></item><item><title>What's in a name?</title><link>http://blogs.msdn.com/monad/archive/2006/04/25/583333.aspx#584546</link><pubDate>Thu, 27 Apr 2006 01:01:17 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:584546</guid><dc:creator>(e)Mail Insecurity</dc:creator><description /></item><item><title>re: Windows PowerShell (Monad) Has Arrived</title><link>http://blogs.msdn.com/monad/archive/2006/04/25/583333.aspx#585021</link><pubDate>Thu, 27 Apr 2006 16:12:30 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:585021</guid><dc:creator>andy</dc:creator><description>Sorry, but I found it to be quite sad to read the new name of such a GREAT product. At least rename PowerShell.exe to psh.exe, so it is a bit more hidden :) And from psh.exe we can say phish, fish or some other *fun* name. PowerShell is just as boring as &amp;quot;Microsoft Windows Power Player&amp;quot;.&lt;br&gt;&lt;br&gt;Once again, sorry. You should get as good marketers as you have designers for this product! The only correct thing the &amp;quot;marketers&amp;quot; did here was to recognize that Monad indeed kicks ass :)&lt;br&gt;&lt;br&gt;&lt;br&gt;Mike: People writing scripts and (probably the same) people who are tired of clicking themself to death loves CLI tools. Happily, as Jeffrey wrote above, psh gives us a foundation to provide both worlds. Monad/PowerShell is Janus (&lt;a rel="nofollow" target="_new" href="http://en.wikipedia.org/wiki/Janus_%28mythology%29"&gt;http://en.wikipedia.org/wiki/Janus_%28mythology%29&lt;/a&gt;) .</description></item><item><title>Monad / PowerShell: bl&amp;amp;#237;ž&amp;amp;#237; se fin&amp;amp;#225;ln&amp;amp;#237; verze!</title><link>http://blogs.msdn.com/monad/archive/2006/04/25/583333.aspx#585032</link><pubDate>Thu, 27 Apr 2006 16:36:46 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:585032</guid><dc:creator>TechNet Blog CZ, SK</dc:creator><description>Bl&amp;amp;#237;ž&amp;amp;#237; se fin&amp;amp;#225;ln&amp;amp;#237; verze produktu, kter&amp;amp;#253; se k&amp;amp;#243;dově označuje jako MONAD. Jeho nov&amp;amp;#233; jm&amp;amp;#233;no je PowerShell!...</description></item><item><title>re: Windows PowerShell (Monad) Has Arrived</title><link>http://blogs.msdn.com/monad/archive/2006/04/25/583333.aspx#585718</link><pubDate>Fri, 28 Apr 2006 07:08:32 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:585718</guid><dc:creator>cbowers</dc:creator><description>To Jeff and the entire Monad team - thanks for such a fantastic commandline environment. &amp;nbsp;I can't wait for the other teams @ MS to get with the program to the extent that the E12 guys have.&lt;br&gt;&lt;br&gt;Great stuff!&lt;br&gt;</description></item><item><title>re: Windows PowerShell (Monad) Has Arrived</title><link>http://blogs.msdn.com/monad/archive/2006/04/25/583333.aspx#586649</link><pubDate>Sat, 29 Apr 2006 15:05:35 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:586649</guid><dc:creator>Tomislav</dc:creator><description>PowerShell is great. Do you have t-shirt with PowerShell moto like &amp;quot;You think it.You type it. You get it.&amp;quot; - MS PowerShell. </description></item><item><title>re: Windows PowerShell (Monad) Has Arrived</title><link>http://blogs.msdn.com/monad/archive/2006/04/25/583333.aspx#590831</link><pubDate>Fri, 05 May 2006 18:54:45 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:590831</guid><dc:creator>Ralph Elmerick</dc:creator><description>Now if only the link url's worked to get the RC1 code downloaded. &amp;nbsp;I have been running Monad for months now.&lt;br&gt; &lt;br&gt;&lt;a rel="nofollow" target="_new" href="http://go.microsoft.com/fwlink/?linkid=64772&amp;amp;clcid=0x409"&gt;http://go.microsoft.com/fwlink/?linkid=64772&amp;amp;clcid=0x409&lt;/a&gt; &lt;br&gt; &lt;br&gt;</description></item><item><title>Download link broken</title><link>http://blogs.msdn.com/monad/archive/2006/04/25/583333.aspx#590883</link><pubDate>Fri, 05 May 2006 20:00:05 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:590883</guid><dc:creator>SunChero</dc:creator><description>i dont know what isxcatly happening , but the link to download powershell or monad or whatever is no longer &amp;nbsp;available , i hope microsoft is not &amp;nbsp;going back away from powershell , and dropping the whole idea ... any info about the futur of &amp;nbsp;powershell ??</description></item><item><title>re: Windows PowerShell (Monad) Has Arrived</title><link>http://blogs.msdn.com/monad/archive/2006/04/25/583333.aspx#590885</link><pubDate>Fri, 05 May 2006 20:01:32 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:590885</guid><dc:creator>SunChero</dc:creator><description>i dont know what isxcatly happening , but the link to download powershell or monad or whatever is no longer &amp;nbsp;available , i hope microsoft is not &amp;nbsp;going back away from powershell , and dropping the whole idea ... any info about the futur of &amp;nbsp;powershell ??</description></item><item><title>re: Windows PowerShell (Monad) Has Arrived</title><link>http://blogs.msdn.com/monad/archive/2006/04/25/583333.aspx#590890</link><pubDate>Fri, 05 May 2006 20:06:09 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:590890</guid><dc:creator>Wassim</dc:creator><description>Hi,&lt;br&gt;Thank you for reporting this issue. The product team is aware of this and is working hard and doing everything possible to fix this problem in a timely manner. We do apologize for any inconvenience this might have caused.&lt;br&gt;&lt;br&gt;Wassim&lt;br&gt;[MSFT]</description></item><item><title>re: Windows PowerShell (Monad) Has Arrived</title><link>http://blogs.msdn.com/monad/archive/2006/04/25/583333.aspx#591992</link><pubDate>Sun, 07 May 2006 23:37:42 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:591992</guid><dc:creator>morten</dc:creator><description>PowerShell (Monad) is great, but how can I intergrate all this functionality into my DotNet apps?&lt;br&gt;&lt;br&gt;/Morten</description></item><item><title>re: Windows PowerShell (Monad) Has Arrived</title><link>http://blogs.msdn.com/monad/archive/2006/04/25/583333.aspx#592009</link><pubDate>Mon, 08 May 2006 00:21:49 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:592009</guid><dc:creator>PowerShellTeam</dc:creator><description>&amp;gt; how can I intergrate all this functionality into my DotNet apps? &lt;br&gt;&lt;br&gt;By linking the PowerShell DLLs into your app and calling the RunSpace APIs.&lt;br&gt;&lt;a rel="nofollow" target="_new" href="http://windowssdk.msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref13/html/n_system_management_automation_runspaces.asp"&gt;http://windowssdk.msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref13/html/n_system_management_automation_runspaces.asp&lt;/a&gt;&lt;br&gt;&lt;br&gt;&lt;a rel="nofollow" target="_new" href="http://blogs.msdn.com/monad/archive/2006/02/01/522546.aspx"&gt;http://blogs.msdn.com/monad/archive/2006/02/01/522546.aspx&lt;/a&gt;&lt;br&gt;&lt;br&gt;Jeffrey Snover [MSFT]&lt;br&gt;Windows PowerShell Architect</description></item><item><title>re: Windows PowerShell (Monad) Has Arrived</title><link>http://blogs.msdn.com/monad/archive/2006/04/25/583333.aspx#599332</link><pubDate>Wed, 17 May 2006 00:34:34 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:599332</guid><dc:creator>Peter Monadjemi</dc:creator><description>PowerShell is a breakthrough technology and for many, many admins around world who never got full power with WSH and VBScript a dream comes trough.&lt;br&gt;&lt;br&gt;I can't believe that some people here have time to complain about the naming (but it really should be psh.exe by the away)</description></item><item><title>re: Windows PowerShell (Monad) Has Arrived</title><link>http://blogs.msdn.com/monad/archive/2006/04/25/583333.aspx#600553</link><pubDate>Thu, 18 May 2006 05:41:31 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:600553</guid><dc:creator>ricka</dc:creator><description>Happy days indeed. When the only thing we can complain about is the name :)&lt;br&gt;&lt;br&gt;Why don't you just include a flag, or script so on first invocation you can &lt;br&gt;PowerShell /hl psh&lt;br&gt;(ie, create a hard link, or .bat or .cmd, however you want to). A much better approach than psh.exe calling PowerShell.exe&lt;br&gt;Now when I go to a new system, I'm only burdened with the arduous task of typing P O W E R S H E L L once.&lt;br&gt;--ricka</description></item><item><title>Can Live   &amp;raquo; Blog Archive   &amp;raquo; Windows PowerShell: Monad leaves Microsoft Building</title><link>http://blogs.msdn.com/monad/archive/2006/04/25/583333.aspx#7103225</link><pubDate>Mon, 14 Jan 2008 02:47:42 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:7103225</guid><dc:creator>Can Live   » Blog Archive   » Windows PowerShell: Monad leaves Microsoft Building</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://canlive.net/windows-powershell-monad-leaves.html"&gt;http://canlive.net/windows-powershell-monad-leaves.html&lt;/a&gt;&lt;/p&gt;
</description></item><item><title>Software Information &amp;raquo; Monad : Windows PowerShell (Monad) Has Arrived</title><link>http://blogs.msdn.com/monad/archive/2006/04/25/583333.aspx#7242815</link><pubDate>Fri, 25 Jan 2008 20:10:07 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:7242815</guid><dc:creator>Software Information » Monad : Windows PowerShell (Monad) Has Arrived</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://softwareinformation.247blogging.info/monad-windows-powershell-monad-has-arrived/"&gt;http://softwareinformation.247blogging.info/monad-windows-powershell-monad-has-arrived/&lt;/a&gt;&lt;/p&gt;
</description></item><item><title>Windows PowerShell: Monad leaves Microsoft Building | Etixet</title><link>http://blogs.msdn.com/monad/archive/2006/04/25/583333.aspx#7572200</link><pubDate>Sun, 10 Feb 2008 02:20:29 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:7572200</guid><dc:creator>Windows PowerShell: Monad leaves Microsoft Building | Etixet</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://www.etixet.com/windows-powershell-monad-leaves.html"&gt;http://www.etixet.com/windows-powershell-monad-leaves.html&lt;/a&gt;&lt;/p&gt;
</description></item><item><title>Windows PowerShell: Monad leaves Microsoft Building | Technology</title><link>http://blogs.msdn.com/monad/archive/2006/04/25/583333.aspx#7702107</link><pubDate>Fri, 15 Feb 2008 01:38:51 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:7702107</guid><dc:creator>Windows PowerShell: Monad leaves Microsoft Building | Technology</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://canlive.net/windows-powershell-monad-leaves-2.html"&gt;http://canlive.net/windows-powershell-monad-leaves-2.html&lt;/a&gt;&lt;/p&gt;
</description></item><item><title> Monad Windows PowerShell Monad Has Arrived | Paid Surveys</title><link>http://blogs.msdn.com/monad/archive/2006/04/25/583333.aspx#9653724</link><pubDate>Fri, 29 May 2009 19:12:08 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9653724</guid><dc:creator> Monad Windows PowerShell Monad Has Arrived | Paid Surveys</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://paidsurveyshub.info/story.php?title=monad-windows-powershell-monad-has-arrived"&gt;http://paidsurveyshub.info/story.php?title=monad-windows-powershell-monad-has-arrived&lt;/a&gt;&lt;/p&gt;
</description></item><item><title> Monad Windows PowerShell Monad Has Arrived | Toe Nail Fungus</title><link>http://blogs.msdn.com/monad/archive/2006/04/25/583333.aspx#9744258</link><pubDate>Sat, 13 Jun 2009 14:57:30 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9744258</guid><dc:creator> Monad Windows PowerShell Monad Has Arrived | Toe Nail Fungus</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://toenailfungusite.info/story.php?id=4984"&gt;http://toenailfungusite.info/story.php?id=4984&lt;/a&gt;&lt;/p&gt;
</description></item><item><title> Monad Windows PowerShell Monad Has Arrived | debt consolidator</title><link>http://blogs.msdn.com/monad/archive/2006/04/25/583333.aspx#9788986</link><pubDate>Fri, 19 Jun 2009 18:15:51 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9788986</guid><dc:creator> Monad Windows PowerShell Monad Has Arrived | debt consolidator</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://mydebtconsolidator.info/story.php?id=18987"&gt;http://mydebtconsolidator.info/story.php?id=18987&lt;/a&gt;&lt;/p&gt;
</description></item></channel></rss>